make tests process failures using cross-test-ssh

[Matthew Fortune]

Joseph Myers <joseph@codesourcery.com> writes:
> On Thu, 11 Feb 2016, Steve Ellcey wrote:
> 
> > 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 think Roland has done something like that for NaCl testing.  I've done
> things like that involving a complicated set of scripts to send commands
> over a socket to allow a DejaGnu board file to be used for running tests
> from non-DejaGnu testsuites, but not anything convenient to use in a
> standalone way like cross-test-ssh.sh.

I've done qemu user space testing by simply setting a test
wrapper to structure the command so that it suits how the
environment etc needs to be presented to qemu. It didn't
work brilliantly though as a number of the pthread cond
tests crashed, spuriously failed or took out the host kernel.
There were a variety of other issues too that did not occur
when running with a real kernel. I know of a few people trying
to sure up the user mode emulation in qemu but no massive
leaps forward.

Matthew