Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] support/testing: add runtime test for Crudini (py2 and py3)
Date: Wed, 5 Feb 2020 16:44:30 +0100	[thread overview]
Message-ID: <20200205164430.7c4c4b47@windsurf> (raw)
In-Reply-To: <20200205141149.20749-4-titouan.christophe@railnova.eu>

On Wed,  5 Feb 2020 15:11:49 +0100
Titouan Christophe <titouan.christophe@railnova.eu> wrote:

> This also adds the new tests to the gitlab CI configuration.
> 
> Signed-off-by: Titouan Christophe <titouan.christophe@railnova.eu>
> ---
>  .gitlab-ci.yml                                |  2 +
>  support/testing/tests/package/test_crudini.py | 40 +++++++++++++++++++
>  2 files changed, 42 insertions(+)
>  create mode 100644 support/testing/tests/package/test_crudini.py

We like to have an entry in the DEVELOPERS file for tests so that you
receive an e-mail notification when the test fails in our CI.

> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index c0140527db..aa64bb5fee 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -375,6 +375,8 @@ tests.init.test_systemd.TestInitSystemSystemdRwFull: { extends: .runtime_test }
>  tests.init.test_systemd.TestInitSystemSystemdRwIfupdown: { extends: .runtime_test }
>  tests.init.test_systemd.TestInitSystemSystemdRwNetworkd: { extends: .runtime_test }
>  tests.package.test_atop.TestAtop: { extends: .runtime_test }
> +tests.package.test_crudini.TestCrudiniPy2: {extends: .runtime_test}
> +tests.package.test_crudini.TestCrudiniPy3: {extends: .runtime_test}

You wrote this by hand, but it is auto-generated by "make
.gitlab-ci.yml", with a slightly different formatting.

> +class TestCrudiniBase(TestPythonPackageBase):
> +    config = TestPythonPackageBase.config + "\nBR2_PACKAGE_CRUDINI=y"

We like to use multiline strings to add config options.

I've fixed the above issues and applied to master.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2020-02-05 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 14:11 [Buildroot] [PATCH 0/3] package/crudini: make it Python3 compatible Titouan Christophe
2020-02-05 14:11 ` [Buildroot] [PATCH 1/3] package/python-iniparse: bump to version 0.5 Titouan Christophe
2020-02-05 15:42   ` Thomas Petazzoni
2020-02-05 14:11 ` [Buildroot] [PATCH 2/3] package/crudini: bump to version 0.9.3 Titouan Christophe
2020-02-05 15:43   ` Thomas Petazzoni
2020-02-05 14:11 ` [Buildroot] [PATCH 3/3] support/testing: add runtime test for Crudini (py2 and py3) Titouan Christophe
2020-02-05 15:44   ` Thomas Petazzoni [this message]

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=20200205164430.7c4c4b47@windsurf \
    --to=thomas.petazzoni@bootlin.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