From: DJ Delorie <dj@redhat.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: linux-snps-arc@lists.infradead.org, libc-alpha@sourceware.org,
ahajkova@redhat.com
Subject: Re: How to elf/tst-ldconfig-* in cross test setup
Date: Wed, 11 Mar 2020 18:28:37 -0400 [thread overview]
Message-ID: <xntv2u4jca.fsf@greed.delorie.com> (raw)
In-Reply-To: <e92a698d-1378-5990-d7f8-05c27c5bd689@synopsys.com> (message from Vineet Gupta on Wed, 11 Mar 2020 22:21:58 +0000)
Vineet Gupta <Vineet.Gupta1@synopsys.com> writes:
>> $ 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"); <----
That's inside test-container.c and should be referring to the
test-root's root (i.e. <full path to>/br/build/glibc-867196a7635/testroot.root/lock.fd
Is there a UID mismatch between the two systems? Did you run a full
"make check" at least once, to build the initial testroot? It does a
full "make install" into $build/testroot.pristine/ to use as the basis
for the container's root.
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2020-03-11 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 19:56 How to elf/tst-ldconfig-* in cross test setup Vineet Gupta
2020-03-11 21:36 ` DJ Delorie
2020-03-11 21:50 ` Vineet Gupta
2020-03-11 22:07 ` DJ Delorie
2020-03-11 22:14 ` Vineet Gupta
2020-03-11 22:21 ` Vineet Gupta
2020-03-11 22:28 ` DJ Delorie [this message]
2020-03-11 22:38 ` Vineet Gupta
2020-03-11 22:56 ` Vineet Gupta
2020-03-12 0:53 ` Vineet Gupta
2020-03-11 22:23 ` DJ Delorie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xntv2u4jca.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=ahajkova@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.