This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Chroot testsuite
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Ryan Arnold <ryan dot arnold at linaro dot org>
- Cc: Carlos O'Donell <carlos at redhat dot com>, OndÅej BÃlka <neleai at seznam dot cz>, Will Newton <will dot newton at linaro dot org>, GNU C Library <libc-alpha at sourceware dot org>, Robert Savoye <rob dot savoye at linaro dot org>, Matthew Gretton-Dann <matthew dot gretton-dann at linaro dot org>
- Date: Thu, 16 Jan 2014 18:57:02 +0000
- Subject: Re: Chroot testsuite
- Authentication-results: sourceware.org; auth=none
- References: <52A6732E dot 4030905 at redhat dot com> <CANu=DmgWNhyxq9vE37bvvD=PrDrfi0Y+eAMv0i2KZPxaEnEOxw at mail dot gmail dot com> <20131210111201 dot GA5309 at domone dot podge> <52A764F3 dot 60501 at redhat dot com> <CAJE4xBMs-Qz4J01Z7M4ebwA11MZ_Uf6vdbSJ-GyCuZHbWNCFjw at mail dot gmail dot com> <52B3C775 dot 4070503 at redhat dot com> <CAJE4xBOBfyPsXpW9JMmDd7D2uS-BkJ019+Lsrsxu0Ydg+XvVvw at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1401110109210 dot 16742 at digraph dot polyomino dot org dot uk> <CAJE4xBNKPXPhSWkCGsHm3j=k8pHDE+rjN-tjv82r3fX9WmH8gw at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1401120030510 dot 11301 at digraph dot polyomino dot org dot uk> <CAJE4xBPbDrKiGUmQ+pGtM+msdwc8OMJH0WLD2zREbZ=i_qko2w at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1401140201400 dot 29865 at digraph dot polyomino dot org dot uk> <CAJE4xBNw0v94GXwFf=+6CJP2oK=NqO5hWi4ZYzP3za73DDGQMA at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1401160058250 dot 27886 at digraph dot polyomino dot org dot uk> <CAJE4xBOn7CMtRs-e_dMYmz1sRuP1Q1bHoK-pUZc44Y7ia9PAjA at mail dot gmail dot com>
On Thu, 16 Jan 2014, Ryan Arnold wrote:
> But preferably make check, as you've described it in (d) above, would
> be able to 'install' the binary remotely. Where does it install the
> binaries? In <build-dir>/install-tests directly?
I'd imagine the temporary location for test binaries and their inputs and
outputs would be separate from the copy of the install_root, so the latter
can remain read-only during the testing, when not doing chroot testing.
--
Joseph S. Myers
joseph@codesourcery.com