From: Andreas Ziegler <br025@umbiko.net>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org, Marcus Hoffmann <buildroot@bubu1.eu>
Subject: Re: [Buildroot] [PATCH v2 04/11] support/testing: add test data for mpd (1/6)
Date: Mon, 17 Aug 2026 11:27:54 +0000 [thread overview]
Message-ID: <5cefbba7714f52842a7b47d665394e61@umbiko.net> (raw)
In-Reply-To: <aoKxCBccdMnLPUR_@windsurf>
On 2026-08-17 06:59, Thomas Petazzoni wrote:
> On Mon, Aug 17, 2026 at 03:47:47AM +0000, Andreas Ziegler wrote:
>
>> I will put the test data in a repository and download it during the
>> build.
>> It needs to be present at the start of the system, otherwise more
>> effort is
>> needed to integrate it.
>
> But what is that test data? Why does it need to be more special that
> normal music files?
Because of legal issues I cannot use (copyrighted) existing music files.
I do not like online download sites, because it's difficult to predict
what you get. So I prepared some audio files, containing test signals,
which are tagged to resemble music files. The whole thing needs a
structure (aka directory tree), because it is also intended to validate
correct indexing by mpd.
The runtime test is just a very basic representation of what I normally
do to validate the correct function of a fresh build.
>> Any reason to use a complete package? Download via post-build.sh could
>> also
>> be an option ...
>
> Because we don't want random downloads to happen during the build, as
> it breaks "make source", "make legal-info", it doesn't have
> hash-checking, etc.
Understood.
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com
Kind regards,
Andreas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-17 11:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 11:08 [Buildroot] [PATCH v2 00/11] add runtime test for mpd Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 01/11] package/mpd: install provided sample configuration file as mpd.conf Andreas Ziegler
2026-08-15 17:08 ` Thomas Petazzoni via buildroot
2026-08-17 3:18 ` Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 02/11] package/mpd: remove duplicated dependencies from sub-options Andreas Ziegler
2026-08-15 19:37 ` Thomas Petazzoni via buildroot
2026-08-17 3:27 ` Andreas Ziegler
2026-08-17 3:31 ` Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 03/11] package/mpd: reorder config items based on order in meson_options.txt Andreas Ziegler
2026-08-15 19:38 ` Thomas Petazzoni via buildroot
2026-08-17 3:40 ` Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 04/11] support/testing: add test data for mpd (1/6) Andreas Ziegler
2026-08-15 19:41 ` Thomas Petazzoni via buildroot
2026-08-17 3:47 ` Andreas Ziegler
2026-08-17 6:59 ` Thomas Petazzoni via buildroot
2026-08-17 11:27 ` Andreas Ziegler [this message]
2026-08-17 12:14 ` Thomas Petazzoni via buildroot
2026-07-09 11:08 ` [Buildroot] [PATCH v2 05/11] support/testing: add test data for mpd (2/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 06/11] support/testing: add test data for mpd (3/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 07/11] support/testing: add test data for mpd (4/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 08/11] support/testing: add test data for mpd (5/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 09/11] support/testing: add test data for mpd (6/6) Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 10/11] support/testing: add runtime test for mpd Andreas Ziegler
2026-07-09 11:08 ` [Buildroot] [PATCH v2 11/11] DEVELOPERS: add entry for test_mpd Andreas Ziegler
2026-07-11 10:24 ` [Buildroot] [PATCH v2 00/11] add runtime test for mpd Fiona Klute via buildroot
2026-07-12 2:54 ` Andreas Ziegler
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=5cefbba7714f52842a7b47d665394e61@umbiko.net \
--to=br025@umbiko.net \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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