public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@aarsen.me>
To: "Frank Ch. Eigler" <fche@elastic.org>
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 17:05:45 +0100	[thread overview]
Message-ID: <8635advcbu.fsf@aarsen.me> (raw)
In-Reply-To: <Y3pIZSnH99A/+Ddy@elastic.org>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]


"Frank Ch. Eigler" <fche@elastic.org> writes:

> 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.

I tried to see how this works for debugedit, since it uses the make
check steps too, and I noticed that the files are also not preserved
there.  I've come up with the conclusion that it works there because
buildbot will watch a file specified in logfiles= in a build step, so it
doesn't matter whether it gets deleted.  See:
https://docs.buildbot.net/current/manual/configuration/steps/shell_command.html

This feels somewhat fragile, but it has worked for a while this way, I
suppose.

That answers that.

Thanks!  Have a great day.
-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]

  reply	other threads:[~2022-11-20 16:07 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
2022-11-20 16:05           ` Arsen Arsenović [this message]
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=8635advcbu.fsf@aarsen.me \
    --to=arsen@aarsen.me \
    --cc=buildbot@sourceware.org \
    --cc=fche@elastic.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).