From: "Frank Ch. Eigler" <fche@elastic.org>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: "Jose E. Marchesi" <jemarch@gnu.org>,
"Arsen Arsenović via poke-devel" <poke-devel@gnu.org>,
positron@gnu.org, buildbot@sourceware.org
Subject: Re: [PATCH builder.git] master.cfg: add GNU poke builder
Date: Sun, 20 Nov 2022 10:31:49 -0500 [thread overview]
Message-ID: <Y3pIZSnH99A/+Ddy@elastic.org> (raw)
In-Reply-To: <867czpvfo8.fsf@aarsen.me>
Hi -
> make V=1 -j 17
> make -j17 V=1 check
The .log/.sum files from this should stick around in the build tree
testsuite/ directory, and one could insert a bunsen file upload step
at this point.
> make -j17 V=1 distcheck
>
> There's no resulting .log anywhere that ``find .'' could reach.
I see what you mean, the poke-2.4 and its _build etc subdirs are all
nuked.
> I tried working around this by setting am__post_remove_distdir, but
> that'd get inherited by the distcleancheck step and break it. I'm not
> aware of a way to pass variables to just the top level make invocation.
If you want to keep distcheck, you may be stuck with having to use the
custom AM_DISTCHECK_CONFIGURE_FLAGS and propagate an autoconf/automake
conditional to trigger a post-"check" copy of the
poke-2.4/_build/sub/testsuite directory out to a preserved location.
- FChE
next prev parent reply other threads:[~2022-11-20 15:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 23:36 Arsen Arsenović
2022-11-20 11:48 ` Jose E. Marchesi
2022-11-20 12:21 ` Arsen Arsenović
2022-11-20 13:17 ` Frank Ch. Eigler
2022-11-20 14:43 ` Arsen Arsenović
2022-11-20 15:31 ` Frank Ch. Eigler [this message]
2022-11-20 16:05 ` Arsen Arsenović
2022-11-20 14:12 ` Jose E. Marchesi
2022-11-23 0:37 ` Mark Wielaard
2022-11-23 11:53 ` Jose E. Marchesi
2022-11-23 17:44 ` Mark Wielaard
2022-11-23 20:20 ` Mohammad-Reza Nabipoor
2022-11-24 12:11 ` Mark Wielaard
2022-11-28 16:48 ` Frank Ch. Eigler
2022-11-28 19:09 ` Arsen Arsenović
2022-11-28 21:53 ` Frank Ch. Eigler
2022-11-29 11:55 ` Mohammad-Reza Nabipoor
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=Y3pIZSnH99A/+Ddy@elastic.org \
--to=fche@elastic.org \
--cc=arsen@aarsen.me \
--cc=buildbot@sourceware.org \
--cc=jemarch@gnu.org \
--cc=poke-devel@gnu.org \
--cc=positron@gnu.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).