This is the mail archive of the
mailing list for the glibc project.
Re: make tests process failures using cross-test-ssh
- From: Steve Ellcey <sellcey at imgtec dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 11 Feb 2016 15:10:59 -0800
- Subject: Re: make tests process failures using cross-test-ssh
- Authentication-results: sourceware.org; auth=none
- References: <1455142589 dot 29579 dot 39 dot camel at ubuntu-sellcey> <alpine dot DEB dot 2 dot 10 dot 1602102248440 dot 11453 at digraph dot polyomino dot org dot uk> <1455147723 dot 29579 dot 51 dot camel at ubuntu-sellcey> <alpine dot DEB dot 2 dot 10 dot 1602110031310 dot 11453 at digraph dot polyomino dot org dot uk> <1455214325 dot 29579 dot 74 dot camel at ubuntu-sellcey> <alpine dot DEB dot 2 dot 10 dot 1602111823360 dot 29940 at digraph dot polyomino dot org dot uk>
- Reply-to: <sellcey at imgtec dot com>
On Thu, 2016-02-11 at 18:28 +0000, Joseph Myers wrote:
> On Thu, 11 Feb 2016, Steve Ellcey wrote:
> > I would like to change this so that the touch is also done on the target
> > machine but I am not sure what macros I should use to in order to have
> > cross-test-ssh.sh run touch.
> In general you should not assume it's possible to run arbitrary commands
> on the system running the newly built glibc; remember, the test wrapper
> could be an emulator such as userspace QEMU. By design, the testsuite
> runs as little as possible on the system running the newly built glibc:
> only programs newly built and linked against it (possibly via "env", but
> that's just a default definition).
Have you (or anyone else) used userspace qemu to do glibc testing? Is
there a script like cross-test-ssh.sh to plug in as the test-wrapper?
I already use qemu for GCC testing so that would be a good way for me to
test if I can get it to work.