From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: DJ Delorie <dj@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
Libc-alpha <libc-alpha@sourceware.org>
Subject: Buildbot improvements
Date: Tue, 13 Jul 2021 15:18:30 -0300 [thread overview]
Message-ID: <845a9c6b-b691-f31c-d789-c61d7bf31fce@linaro.org> (raw)
Hi DJ,
First thanks for setting up the CL/CI initiative for the glibc buildbots,
it is really helpful. Carlos has asked to reach you to improve the
trybots dump log, so it would include additional information the patch
sender might use to reproduce the issue.
One thing is the configure line, either the config.log from configure or
at least the command itself (similar to what build-many-glibcs.py do).
I think build system information, such as compiler version and other tools,
can be inferred from the make.log.
Another thing is the machine information itself, such the architecture,
the kernel, and other pieces that might help the developer to figure out
the possible cause of the regression.
Another nice thing to have would be to dump a line where one could use
to download the container used to run the tests to reproduce it locally
(it would still be subject to underlying kernel).
Besides this I think you might want to tune the container your are using,
since a recent regression [1] seems to be a limitation of the total number
of threads (I have seem it before running glibc make check insider docker
containers).
https://www.delorie.com/trybots/32bit/2492/nptl-tst-audit-threads.out
next reply other threads:[~2021-07-13 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 18:18 Adhemerval Zanella [this message]
2021-07-13 19:15 ` DJ Delorie
2021-07-14 20:43 ` Carlos O'Donell
2021-07-14 21:10 ` DJ Delorie
2021-07-14 21:58 ` Adhemerval Zanella
2021-07-15 4:11 ` DJ Delorie
2021-07-15 12:24 ` Carlos O'Donell
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=845a9c6b-b691-f31c-d789-c61d7bf31fce@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=libc-alpha@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).