From: Ricardo Martincoski <ricardo.martincoski@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] testing: add python-cryptography tests
Date: Sun, 17 Sep 2017 02:26:12 -0300 [thread overview]
Message-ID: <59be07745ff02_17f3141de70515ce@ultri3.mail> (raw)
In-Reply-To: 5d8ea4ebb51023d3943fb4e5a1678f8cfba70527.1505594291.git.yann.morin.1998@free.fr
Hello,
On Sat, Sep 16, 2017 at 05:38 PM, Yann E. MORIN wrote:
> testing: add python-cryptography tests
This patch could now be renamed to:
python-cryptography: add runtime tests
or something like this
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> Reviewed-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
> [yann.morin.1998 at free.fr:
> - move to package directory,
- rename the test file to follow the package convention,
I am OK with this change, but I think it worth mentioning.
> - indent the config fragment
> ]
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
>
> ---
> Note:
> This is exactly the same as https://patchwork.ozlabs.org/patch/811011/
> but with the test moved to the python-cryptography package and the
> config fragment indented.
> ---
> .gitlab-ci.yml | 2 ++
> package/python-cryptography/python-cryptography.py | 31 ++++++++++++++++++++++
> 2 files changed, 33 insertions(+)
> create mode 100644 package/python-cryptography/python-cryptography.py
.gitlab-ci.yml needs to be generated again because of this rename (to use '-'
in the name again).
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index b44c935f2a..091b016191 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -250,6 +250,8 @@ tests.package.test_ipython.TestIPythonPy2: *runtime_test
> tests.package.test_ipython.TestIPythonPy3: *runtime_test
> tests.package.test_python.TestPython2: *runtime_test
> tests.package.test_python.TestPython3: *runtime_test
> +tests.package.test_python_cryptography.TestPythonPy2Cryptography: *runtime_test
> +tests.package.test_python_cryptography.TestPythonPy3Cryptography: *runtime_test
> tests.toolchain.test_external.TestExternalToolchainBuildrootMusl: *runtime_test
> tests.toolchain.test_external.TestExternalToolchainBuildrootuClibc: *runtime_test
> tests.toolchain.test_external.TestExternalToolchainCCache: *runtime_test
[snip]
Regards,
Ricardo
next prev parent reply other threads:[~2017-09-17 5:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 20:38 [Buildroot] [PATCH 0/2] support/run-test: move pacakges' tests to packages' directories Yann E. MORIN
2017-09-16 20:38 ` [Buildroot] [PATCH 1/2] support/run-tests: move packages tests to packages directories Yann E. MORIN
2017-09-17 5:20 ` Ricardo Martincoski
2017-09-17 7:18 ` Yann E. MORIN
2017-09-17 7:52 ` Yann E. MORIN
2017-10-02 0:54 ` Ricardo Martincoski
2017-10-02 5:32 ` Yann E. MORIN
2017-10-02 20:33 ` Ricardo Martincoski
2017-09-16 20:38 ` [Buildroot] [PATCH 2/2] testing: add python-cryptography tests Yann E. MORIN
2017-09-17 5:26 ` Ricardo Martincoski [this message]
2017-09-17 7:19 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59be07745ff02_17f3141de70515ce@ultri3.mail \
--to=ricardo.martincoski@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox