From: Chuck Lever <chuck.lever@oracle.com>
To: Scott Mayhew <smayhew@redhat.com>
Cc: kdevops@lists.linux.dev
Subject: Re: [PATCH 2/2] gitr: Make gitr work on RHEL/CentOS
Date: Wed, 4 Sep 2024 14:38:10 -0400 [thread overview]
Message-ID: <ZtipEnjJp6sal+ml@tissot.1015granger.net> (raw)
In-Reply-To: <Ztih5SKSwrhNhHPx@aion>
On Wed, Sep 04, 2024 at 02:07:33PM -0400, Scott Mayhew wrote:
> On Wed, 04 Sep 2024, Chuck Lever wrote:
> > With stock kdevops, I'm seeing some gitr failures (eg, t6300) on
> > Fedora 40 that were not there on Fedora 39. Wondering if this series
> > might help with that.
>
> Unfortunately no - the only effect that these patches should have on
> Fedora is that the devconfig playbook is no longer accidentally
> installing extra packages.
>
> I'm seeing this failures on 6.10.6-200.fc40.x86_64:
>
> Test Summary Report
> -------------------
> ./t6300-for-each-ref.sh (Wstat: 256 (exited 1) Tests: 418 Failed: 3)
> Failed tests: 35, 107-108
> Non-zero exit status: 1
> ./t9001-send-email.sh (Wstat: 256 (exited 1) Tests: 199 Failed: 4)
> Failed tests: 37, 48-50
> Non-zero exit status: 1
> Files=999, Tests=29254, 1711 wallclock secs (17.16 usr 4.92 sys + 1259.25 cusr 2402.60 csys = 3683.93 CPU)
> Result: FAIL
>
> and the *.stderr files have no info in them at all.
Aye, that's what I see on F40.
--
Chuck Lever
prev parent reply other threads:[~2024-09-04 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 14:48 [PATCH 1/2] devconfig/redhat: Fix up a few issues with the install-deps playbook Scott Mayhew
2024-09-03 14:48 ` [PATCH 2/2] gitr: Make gitr work on RHEL/CentOS Scott Mayhew
2024-09-04 15:38 ` Chuck Lever
2024-09-04 18:07 ` Scott Mayhew
2024-09-04 18:38 ` Chuck Lever [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=ZtipEnjJp6sal+ml@tissot.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
--cc=smayhew@redhat.com \
/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