From: "Frank Ch. Eigler" <fche@elastic.org>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: Mark Wielaard <mark@klomp.org>,
Mohammad-Reza Nabipoor <mnabipoor@gnu.org>,
buildbot@sourceware.org, poke-devel@gnu.org
Subject: Re: [PATCH builder.git] master.cfg: add GNU poke builder
Date: Mon, 28 Nov 2022 16:53:14 -0500 [thread overview]
Message-ID: <Y4UtyjD0873RwaiI@elastic.org> (raw)
In-Reply-To: <86a64aki12.fsf@aarsen.me>
Hi -
> Ah, thanks. I didn't figure those would be needed, sorry abt that ;)
Another suggestion: change your dejagnu .exp files so that the
test name strings passed to "pass" "fail" etc. are persistent
and generic, and not contain irrelevant stuff like a local
complete path name.
That's because having these paths in the test names makes those test
cases different from run to run, and thus the results are not directly
comparable. For example:
https://builder.sourceware.org/testrun-diffs?mode=differences&commitish=4a4313189ff5c3e354c977f8eca6621329af3279&commitish=c6cb32e4a10b994e26e32266eaf7cce47f7128d5
It'd be better just to print the `basename $path` or something like that
instead.
- FChE
next prev parent reply other threads:[~2022-11-28 21:53 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ć
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 [this message]
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=Y4UtyjD0873RwaiI@elastic.org \
--to=fche@elastic.org \
--cc=arsen@aarsen.me \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.org \
--cc=mnabipoor@gnu.org \
--cc=poke-devel@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).