nptl/test-*-printers tests failing

[Steve Ellcey]

On Fri, 2016-12-16 at 14:48 -0800, Steve Ellcey wrote:
> Does anyone else get failures for the new nptl/test-*-printers tests?
> On aarch64, with the standard sources I get these failures:
> 
> FAIL: nptl/test-cond-printers
> FAIL: nptl/test-condattr-printers
> FAIL: nptl/test-mutex-printers
> FAIL: nptl/test-mutexattr-printers
> FAIL: nptl/test-rwlock-printers
> FAIL: nptl/test-rwlockattr-printers

And just after sending the email I found the problem. Â On the machine
I was testing there is no /usr/bin/python. Â There is /usr/bin/python3
which is why I could run build-many-glibcs.py but there was no
/usr/bin/python.

I found this in my log file:

env PYTHONPATH=/home/ubuntu/sellcey/glibc-patched/obj-
glibc64/nptl/:../scripts:${PYTHONPATH} \
    python test-mutexattr-printers.py test-mutexattr-printers.c
/home/ubuntu/sellcey/glibc-patched/obj-glibc64/nptl/test-mutexattr-
printers nptl-printers.py > /home/ubuntu/sellcey/glibc-patched/obj-
glibc64/nptl/test-mutexattr-printers.out; \
../scripts/evaluate-test.sh nptl/test-mutexattr-printers $? false false
> /home/ubuntu/sellcey/glibc-patched/obj-glibc64/nptl/test-mutexattr-
printers.test-result
env: ‘python’: No such file or directory


There should probably be some sort of check for the existence of the
python command as part of these tests.


Steve Ellcey
sellcey@caviumnetworks.com