Vineet Gupta <Vineet.Gupta1@xxxxxxxxxxxx> writes: > No, I'm running this is a cross-compiled setup where the test artifacts are on a > NFS mounted host. Here's the full strace for test > > > $ strace_static -f > ~/br/build/glibc-867196a7635/build/elf/tst-ldconfig-ld_so_conf-update This is a manual run. Even with a cross setup, you still run test-container on the cross target: $ strace_static -f ~/br/build/glibc-867196a7635/build/support/test-container \ ~/br/build/glibc-867196a7635/build/elf/tst-ldconfig-ld_so_conf-update The containerized tests are (in this case) containerized because they rely on setup files (like /etc/ld.so.conf) inside the container to run the test. Otherwise you end up corrupting the host OS. The test infrastructure knows how to run containerized tests on remote machines, though... any reason why you're not using that setup? Note: if containers aren't yet supported on your platform, it's OK to just skip those tests. Also, it's not always a good idea to run a containerized test outside the container; the tests assume they can trash the container as part of the test. _______________________________________________ linux-snps-arc mailing list linux-snps-arc@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/linux-snps-arc
