From: 邓尧 <torshie@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Release test framework
Date: Wed, 4 Dec 2013 13:51:42 +0800 [thread overview]
Message-ID: <CAOb3iughuEJ0BGXf5NhfOwPFt8hed9WBQNyUU0YVtTG=n+=G0g@mail.gmail.com> (raw)
In-Reply-To: <20131203221153.GA18502@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
If busybox is used, the test framework itself would depend on musl-libc,
which means test test framework would depend on the test subject. In
theory, it's a bad bad idea.
0.02$
On Wed, Dec 4, 2013 at 6:11 AM, Rich Felker <dalias@aerifal.cx> wrote:
> One thing that's still missing that I had on the Roadmap for 0.9.15 is
> establishing a formal testing procedure for releasing. Basically what
> I have in mind is:
>
> For each arch:
> Assume the existence of a musl-cross compiler for it.
> Build musl and install to a prefix under the rest root.
> Build libc-test configured to use the new headers/libs.
> Create cpio archive containing:
> Newly built musl libc.so.
> Newly built libc-test tree.
> Provided base system template containing:
> Busybox.
> Simple /etc tree.
> Minimal init script to run tests.
> Boot qemu using a provided kernel and the new initramfs.
> Save output of tests outside the qemu environment.
> Diff against expected results for comparison.
>
> Does this seem like a reasonable and useful test procedure? Is anyone
> willing to volunteer to write the scripts for it?
>
> Rich
>
[-- Attachment #2: Type: text/html, Size: 1741 bytes --]
next prev parent reply other threads:[~2013-12-04 5:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 22:11 Rich Felker
2013-12-04 5:51 ` 邓尧 [this message]
2013-12-04 6:01 ` Rich Felker
2013-12-04 6:22 ` 邓尧
2013-12-04 7:06 ` Rich Felker
2013-12-04 7:16 ` Szabolcs Nagy
2013-12-04 7:48 ` Szabolcs Nagy
2013-12-09 10:56 ` Waldemar Brodkorb
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='CAOb3iughuEJ0BGXf5NhfOwPFt8hed9WBQNyUU0YVtTG=n+=G0g@mail.gmail.com' \
--to=torshie@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).