public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: adhemerval.zanella@linaro.org, libc-alpha@sourceware.org
Subject: Re: Newer hwcap failures
Date: Fri, 29 Jan 2021 01:09:31 -0500	[thread overview]
Message-ID: <xnim7gff50.fsf@greed.delorie.com> (raw)
In-Reply-To: <878s8c1e1v.fsf@oldenburg.str.redhat.com> (message from Florian Weimer on Fri, 29 Jan 2021 06:56:44 +0100)

Florian Weimer <fweimer@redhat.com> writes:
> It's probably a left-over from an earlier non-destructive test in the
> scenarios that are working.

> If so, this is what the postclean flag is for ;-)

To be clearer, I meant, any test that leaves behind an ld.so.cache (or
anything that may affect future tests) should postclean (just in case)
but a test that is sensitive to ld.so.cache should also do a preclean.

This scenario is why I put those features in there.


  parent reply	other threads:[~2021-01-29  6:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 18:47 Adhemerval Zanella
2021-01-28 18:52 ` Adhemerval Zanella
2021-01-28 19:53 ` Florian Weimer
2021-01-28 20:01   ` Adhemerval Zanella
2021-01-28 20:21     ` Adhemerval Zanella
2021-01-28 20:30       ` Adhemerval Zanella
2021-01-28 21:23         ` Adhemerval Zanella
2021-01-28 22:03           ` DJ Delorie
2021-01-29  5:56             ` Florian Weimer
2021-01-29  6:07               ` DJ Delorie
2021-01-29  6:09               ` DJ Delorie [this message]
2021-01-29  9:20           ` Florian Weimer
2021-01-29 10:43             ` Szabolcs Nagy
2021-01-29 10:48               ` Florian Weimer
2021-01-29 10:51                 ` Szabolcs Nagy
2021-01-29 11:53                   ` Adhemerval Zanella
2021-01-29 12:46                     ` H.J. Lu
2021-01-29 12:31                   ` Florian Weimer
2021-01-29 13:06                     ` Adhemerval Zanella

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=xnim7gff50.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).