From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Revert "package/prosody: use correct bit32 package"
Date: Thu, 4 Jun 2020 11:21:44 +0200 [thread overview]
Message-ID: <20200604112144.61489c05@windsurf> (raw)
In-Reply-To: <CAB0FRssoZHBnO329q0vvX-8Yr8MBPMzZrhs7UGLytVn1eo++Dg@mail.gmail.com>
On Thu, 4 Jun 2020 07:00:47 +0200
Fran?ois Perrad <francois.perrad@gadz.org> wrote:
> 2) with BR, it's easy to run a test (even locally, before a commit), but it
> isn't easy to know that a test exists.
> In my point of view, the right place of test_prosody.py is in the directory
> package/prosody, not in support/testing/tests/package,
> support/testing is the right place only for testing infrastructure.
We indeed though about putting tests near packages. However, one issue
is that not all tests are related to packages: some are related to the
core infrastructure, and we wouldn't know where to put those tests. And
it would be even more confusing to have some tests in support/testing/
and some tests in package/. So for now, we have simply kept all tests
in support/testing/, until someone comes up with a better idea :-)
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-04 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 21:59 [Buildroot] [PATCH] Revert "package/prosody: use correct bit32 package" Romain Naour
2020-06-03 22:30 ` James Hilliard
2020-06-03 22:42 ` Romain Naour
2020-06-04 0:18 ` James Hilliard
2020-06-04 21:02 ` Romain Naour
2020-06-04 5:00 ` François Perrad
2020-06-04 9:21 ` Thomas Petazzoni [this message]
2020-06-04 21:28 ` Thomas Petazzoni
2020-06-06 21:34 ` Peter Korsgaard
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=20200604112144.61489c05@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