From: fche@redhat.com (Frank Ch. Eigler)
To: Simon Marchi <simark@simark.ca>
Cc: Jan Vrany <jan@vrany.io>, GDB mailing list <gdb@sourceware.org>
Subject: Re: CI scripts
Date: Wed, 18 Jan 2023 21:42:36 -0500 [thread overview]
Message-ID: <87r0vrnt2b.fsf@redhat.com> (raw)
In-Reply-To: <fcba3134-92a9-85a0-82aa-931473f20f60@simark.ca> (Simon Marchi via Gdb's message of "Thu, 12 Jan 2023 08:55:14 -0500")
Simon Marchi via Gdb <gdb@sourceware.org> writes:
> [...]
>> I'm wondering whether the CI scripts for your job are available?
>> I'd like to setup a similar job on my CI to avoid similar problems
>> in future.
>> [...]
> Yes, it's on Jenkins, the job description (it uses Jenkins Job Builder)
> is here:
>
> https://github.com/simark/lttng-ci/blob/master/jobs/binutils-gdb.yaml
> [...]
> https://github.com/simark/lttng-ci/blob/master/scripts/binutils-gdb/build.sh
(I assume y'all are also aware of https://builder.sourceware.org/, which
runs several gdb build/test variants.)
> It was green for a while (I filter out pre-existing known failures /
> flaky tests in the testsuite, hoping to fix those little by little). [...]
Yeah, that's an interesting problem. We're also addressing it within
the bunsen testsuite data analysis gadget also running here on
sourceware, but hopefully with no hard-coded "false-results" lists
required.
- FChE
prev parent reply other threads:[~2023-01-19 2:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 12:56 Jan Vrany
2023-01-12 13:55 ` Simon Marchi
2023-01-18 12:09 ` Jan Vrany
2023-01-18 13:36 ` Simon Marchi
2023-01-18 16:00 ` Jan Vrany
2023-01-18 16:04 ` Simon Marchi
2023-01-19 2:42 ` Frank Ch. Eigler [this message]
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=87r0vrnt2b.fsf@redhat.com \
--to=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=jan@vrany.io \
--cc=simark@simark.ca \
/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).