public inbox for bunsen@sourceware.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@aarsen.me>
To: bunsen@sourceware.org, builder@sourceware.org
Subject: Automake dist-check and log extraction: runtest --outdir
Date: Wed, 18 Jan 2023 00:00:04 +0100	[thread overview]
Message-ID: <86sfg8iw7d.fsf@aarsen.me> (raw)

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

Hi there,

The make_distcheck_test_suite_step uses a logfiles= keyword arg, which
in turn uses inotify (presumably) to watch a file for a logfile creatd
on it, and to collect info from it.

To my awareness, this has not failed Sourceware yet - however, it is a
fragile mechanism.

DejaGnu provides a way for the directory in which log and sum files are
stored to be altered, see --outdir in
https://www.gnu.org/software/dejagnu/manual/Invoking-runtest.html

This variable is modifiable both through flags passed to runtest and via
Tcl, see
https://gnu.org/s/dejagnu/manual/Command-line-option-variables.html

To test this, I made an adjustment to my ~/.dejagnurc, and ran the GNU
poke testsuite:

  $ cat ~/.dejagnurc 
  set outdir "/tmp/outtest"
  $ make -j17 distcheck
  ...

This, indeed, resulted in a poke.log and poke.sum in the /tmp/outtest
directory.

I believe we should replace the inotify-based mechanism with this method
of redirecting logs.

What do you think?  And, apologies about the lack of patch - I won't be
free for any involved effort at least until the weekend.

Thanks in advance, have a lovely night.
-- 
Arsen Arsenović

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

             reply	other threads:[~2023-01-17 23:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 23:00 Arsen Arsenović [this message]
2023-01-17 23:51 ` Frank Ch. Eigler
2023-01-17 23:57   ` Arsen Arsenović
2023-01-18 15:01     ` Frank Ch. Eigler

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=86sfg8iw7d.fsf@aarsen.me \
    --to=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).