On 3/11/20 3:14 PM, Vineet Gupta wrote:
>> 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?
> I was using that setup all along: this was my original host cmdline:
>
> $ make test-wrapper='<full path
> to>/br/build/glibc-867196a7635/scripts/cross-test-ssh.sh root@192.168.0.20' xcheck
> subdirs=elf
FWIW the original failures were here
lock_fd = open (concat (pristine_root_path, "/lock.fd", NULL),
O_CREAT | O_TRUNC | O_RDWR, 0666);
if (lock_fd < 0)
FAIL_EXIT1 ("Cannot create testroot lock.\n"); <----
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
