Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/6] [RFC] Adds test infrastructure for packages
Date: Sun, 4 Oct 2015 19:35:19 +0100	[thread overview]
Message-ID: <56117167.1070305@mind.be> (raw)
In-Reply-To: <2109934542.250678.1441612831227.JavaMail.zimbra@openwide.fr>

On 07-09-15 09:00, Denis Thulin wrote:
> Hi Arnout,
> 
> ----- Le 7 Sep 15, ? 0:46, Arnout Vandecappelle arnout at mind.be a ?crit :
> 
>> Hi Denis,
>>
>> On 31-08-15 11:59, Denis THULIN wrote:
>>> This patch series adds a test generation infrastructure for packages to
>>> Buildroot.
>>> The generated tests are robotframework tests.
[snip]
>> Bottom line: I'm not in favour of this series either. Of course, the first
>> patch adding python-robotframework is still relevant independently.
> 
> Ok, thanks for the answer  :)

 Hi Denis,

 We discussed this again at the BR Developer meeting in Dublin, and concluded
that we're going to proceed with the simpler and less-invasive unit-test-based
approach. It is in fact already running on Jenkins at [1]. Therefore, I've
marked most of the series as Rejected in patchwork.

 Regarding python-robotframework, as mentioned before, it is still relevant.
However, neither of the two versions you submitted are suitable at the moment:
- the version of [2] is still using 2.9rc1;
- the version of [3] add a host- version which we don't need.
Note that the host-version was not even needed in this series: for something
like this, we expect it to be installed on the system rather than building it.
So these patches are both marked as Changes Requested.

 Regards,
 Arnout

[1] http://jenkins.free-electrons.com/job/buildroot-runtime-tests/
[2] http://patchwork.ozlabs.org/patch/501203/
[3] http://patchwork.ozlabs.org/patch/512420/

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

      reply	other threads:[~2015-10-04 18:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  9:59 [Buildroot] [PATCH 0/6] [RFC] Adds test infrastructure for packages Denis THULIN
2015-08-31  9:59 ` [Buildroot] [PATCH 1/6] python-robotframework: New package Denis THULIN
2015-08-31  9:59 ` [Buildroot] [PATCH 2/6] Adds package test infrastructure Denis THULIN
2015-08-31  9:59 ` [Buildroot] [PATCH 3/6] tests: create variable files through kconfig Denis THULIN
2015-08-31  9:59 ` [Buildroot] [PATCH 4/6] tests: Adds user manual entry Denis THULIN
2015-08-31  9:59 ` [Buildroot] [PATCH 5/6] flask: Adds robotframework tests Denis THULIN
2015-08-31  9:59 ` [Buildroot] [PATCH 6/6] python: Adds tests Denis THULIN
2015-08-31 12:48 ` [Buildroot] [PATCH 0/6] [RFC] Adds test infrastructure for packages Thomas Petazzoni
2015-09-01  9:52   ` Denis Thulin
2015-09-06 22:46 ` Arnout Vandecappelle
2015-09-07  8:00   ` Denis Thulin
2015-10-04 18:35     ` Arnout Vandecappelle [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=56117167.1070305@mind.be \
    --to=arnout@mind.be \
    --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