All of lore.kernel.org
 help / color / mirror / Atom feed
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:07:07 -0400	[thread overview]
Message-ID: <xnzhcm4kc4.fsf@greed.delorie.com> (raw)
In-Reply-To: <1e5222c2-5e79-1cbe-1bc1-ea1c31f920a3@synopsys.com> (message from Vineet Gupta on Wed, 11 Mar 2020 21:50:30 +0000)

Vineet Gupta <Vineet.Gupta1@synopsys.com> 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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

  reply	other threads:[~2020-03-11 22:07 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 [this message]
2020-03-11 22:14       ` Vineet Gupta
2020-03-11 22:21         ` Vineet Gupta
2020-03-11 22:28           ` DJ Delorie
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=xnzhcm4kc4.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.