[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131203221153.GA18502@brightrain.aerifal.cx>
Date: Tue, 3 Dec 2013 17:11:53 -0500
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Release test framework
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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
