[PING 2][PATCH v3] Add pretty printers for the NPTL lock types

[Carlos O'Donell]

On 03/10/2016 03:39 PM, Martin Galvan wrote:
> After dwelling a bit more into the test system, I think I'm beginning
> to understand how the test-wrapper variables work. Correct me if I'm
> wrong but, except for NaCl, most (if not all) the tests should work
> with cross-test-ssh.sh. If that's the case, I think the simplest way
> to do this is to use the gdb that's in the system where the
> cross-glibc runs, and use cross-test-ssh.sh to run my test scripts. If
> required I could check whether Python and gdb actually exist in the
> target, failing with UNSUPPORTED if they don't.

Correct.

You can absolutely do that, return exit code 77 to indicate the test
was UNSUPPORTED.

The alternative is to run the test with a host cross-gdb that talks
to a gdbserver (which you'd have to start as part of the test). It's
certainly easier to just run everything on the target, and that's fine.
 
> Assuming I'm correct, in that case I shouldn't need to define any
> additional variables. test-wrapper should be enough.

Right.

> I'm about to run a cross make check using cross-test-ssh.sh on a
> Beaglebone Black running Debian; hopefully I can later use it to
> cross-tests my printers.

Sounds good.

-- 
Cheers,
Carlos.