Open alllecs opened 8 years ago
Regarding getaddrinfo_01.
Just assign a resolvable hostname to you host.
Or add the current hostname to /etc/hosts:
echo "127.0.0.1 debian" >> /etc/hosts echo "::1 debian" >> /etc/hosts
The input06 messages are red herring here, all it says is that it couldn't test input subsystem because there is no uinput compiled in kernel or as a module.
Looking into the LTP source the test that creates the sandbox directory is testscripts/test_fs_bind.sh
. Most likely something went wrong in the test and something stayed being mounted under the sandbox directory after the test has exited, or the test became stuck before it had chance to clean up and is still running on background.
I suggested that the reason for inconsistent running tests on different architectures. The script test_fs_bind.sh out by mistake after 5 tests. I get tests list of testscripts/test_fs_bind.sh. Arrange running tests starting at 1. The script test_fs_bind.sh not out by mistake. But get this error again.
Run command:
find "testcases/bin/fs_bind/move/" -type f -name 'test*'
result on Mips architecture:
testcases/bin/fs_bind/move/test06
testcases/bin/fs_bind/move/test01
testcases/bin/fs_bind/move/test09
testcases/bin/fs_bind/move/test07
testcases/bin/fs_bind/move/test08
testcases/bin/fs_bind/move/test10
testcases/bin/fs_bind/move/test13
testcases/bin/fs_bind/move/test20
testcases/bin/fs_bind/move/test16
testcases/bin/fs_bind/move/test22
testcases/bin/fs_bind/move/test12
testcases/bin/fs_bind/move/test03
testcases/bin/fs_bind/move/test19
testcases/bin/fs_bind/move/test17
testcases/bin/fs_bind/move/test11
testcases/bin/fs_bind/move/test05
testcases/bin/fs_bind/move/test14
testcases/bin/fs_bind/move/test18
testcases/bin/fs_bind/move/test21
testcases/bin/fs_bind/move/test04
testcases/bin/fs_bind/move/test02
testcases/bin/fs_bind/move/test15
result on Intel:
testcases/bin/fs_bind/move/test14
testcases/bin/fs_bind/move/test13
testcases/bin/fs_bind/move/test11
testcases/bin/fs_bind/move/test09
testcases/bin/fs_bind/move/test21
testcases/bin/fs_bind/move/test03
testcases/bin/fs_bind/move/test19
testcases/bin/fs_bind/move/test17
testcases/bin/fs_bind/move/test04
testcases/bin/fs_bind/move/test05
testcases/bin/fs_bind/move/test06
testcases/bin/fs_bind/move/test22
testcases/bin/fs_bind/move/test20
testcases/bin/fs_bind/move/test18
testcases/bin/fs_bind/move/test15
testcases/bin/fs_bind/move/test10
testcases/bin/fs_bind/move/test16
testcases/bin/fs_bind/move/test08
testcases/bin/fs_bind/move/test02
testcases/bin/fs_bind/move/test07
testcases/bin/fs_bind/move/test01
testcases/bin/fs_bind/move/test12
I add umount "${sandbox}"
in test_fs_bind.sh before rm -rf "${sandbox}"
and fix problem with sandbox but i don't know correct solution.
I have error rm: cannot remove ‘/tmp/ltp-EyOqzruY93/hugz82UVp’: Device or resource busy
still.
Start LTP on Qemu Malta RAM=2048M. Debian Linux 4.6. Сommand run: /opt/ltp/runltp It starts running tests.
After wait for a few hours I get:
I tried to run away from input06 test. This error remains.
How do I avoid the error ? Thanks!