From: Simon Marchi <simark@simark.ca>
To: Jan Vrany <jan@vrany.io>, GDB mailing list <gdb@sourceware.org>
Subject: Re: CI scripts
Date: Thu, 12 Jan 2023 08:55:14 -0500 [thread overview]
Message-ID: <fcba3134-92a9-85a0-82aa-931473f20f60@simark.ca> (raw)
In-Reply-To: <c714b40cb09875cd521d409abb75b5540c82cca3.camel@vrany.io>
On 1/12/23 07:56, Jan Vrany via Gdb wrote:
> Hi Simon,
>
> about a month ago when you helped me with use-after-free fix
> you wrote:
>
>> I ran the patch through my CI job, looks good.
>
> 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.
>
> I'm especially interested in "configure ..." and "make check ..."
> commands.
>
> Thanks!
>
> Jan
>
Hi Jan,
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
The build script is runs is here (which is where the commands you are
intereted in are):
https://github.com/simark/lttng-ci/blob/master/scripts/binutils-gdb/build.sh
The job itself is hosted here:
https://ci.lttng.org/view/GDB/job/binutils-gdb_master_linuxbuild/
It's hosted on my employer's infrastructure, hence why it's on the LTTng
CI.
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). I
usually try to keep it that way by catching regressions early and
notifying people, but it got broken by various commits during the
holidays, so I have to play catch up now.
Simon
next prev parent reply other threads:[~2023-01-12 13:55 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 [this message]
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
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=fcba3134-92a9-85a0-82aa-931473f20f60@simark.ca \
--to=simark@simark.ca \
--cc=gdb@sourceware.org \
--cc=jan@vrany.io \
/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).