From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: bunsen@sourceware.org, builder@sourceware.org
Subject: Re: Automake dist-check and log extraction: runtest --outdir
Date: Wed, 18 Jan 2023 10:01:39 -0500 [thread overview]
Message-ID: <20230118150139.GD10730@redhat.com> (raw)
In-Reply-To: <86ilh4itbq.fsf@aarsen.me>
Hi -
> [...]
> I didn't mean to emphasize the role of inotify at all, rather the role
> of distchecks cleanup of the build directory, which acts as a limit on
> the lifetime of the testsuite results file.
>
> The builder could avoid testsuite files being deleted altogether by
> specifying an outdir outside of distchecks temporary directory.
Ah yes, we have encountered this annoying behaviour before. OK, so
those build jobs that run "make distcheck" in anger could use
"make distcheck RUNTESTFLAGS=--outdir=../foobar" to preserve
test results across the implicit "make distclean".
- FChE
prev parent reply other threads:[~2023-01-18 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 23:00 Arsen Arsenović
2023-01-17 23:51 ` Frank Ch. Eigler
2023-01-17 23:57 ` Arsen Arsenović
2023-01-18 15:01 ` Frank Ch. Eigler [this message]
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=20230118150139.GD10730@redhat.com \
--to=fche@redhat.com \
--cc=arsen@aarsen.me \
--cc=builder@sourceware.org \
--cc=bunsen@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).