From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Chuck Lever III <chuck.lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Cc: Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: git regression failures with v6.2-rc NFS client
Date: Tue, 21 Feb 2023 15:58:55 +0100 [thread overview]
Message-ID: <34432a13-f809-b1a7-e737-e5646880da5d@leemhuis.info> (raw)
In-Reply-To: <108fdc3a-58a1-c32a-efa6-aa0b5645e862@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 03.02.23 13:39, Linux kernel regression tracking (#adding) wrote:
> On 31.01.23 22:15, Chuck Lever III wrote:
>>
>> I upgraded my test client's kernel to v6.2-rc5 and now I get
>> failures during the git regression suite on all NFS versions.
>> I bisected to:
>>
>> 85aa8ddc3818 ("NFS: Trigger the "ls -l" readdir heuristic sooner")
>>
>> The failure looks like:
>> [...]
>
> #regzbot ^introduced 85aa8ddc3818
> #regzbot title nfs: failures during the git regression suite on all NFS
> versions
> #regzbot ignore-activity
#regzbot resolved: corner case Linus was made aware of and apparently
didn't consider something that needs to be fixed
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-02-21 14:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 21:15 git regression failures with v6.2-rc NFS client Chuck Lever III
2023-01-31 22:02 ` Benjamin Coddington
2023-02-01 14:10 ` Benjamin Coddington
2023-02-01 15:53 ` Benjamin Coddington
2023-02-03 14:38 ` Chuck Lever III
2023-02-03 15:13 ` Benjamin Coddington
2023-02-03 15:35 ` Chuck Lever III
2023-02-03 17:14 ` Benjamin Coddington
2023-02-03 18:03 ` Chuck Lever III
2023-02-03 20:01 ` Benjamin Coddington
2023-02-03 20:25 ` Chuck Lever III
2023-02-03 22:26 ` Trond Myklebust
2023-02-03 23:11 ` Chuck Lever III
2023-02-03 23:53 ` Hugh Dickins
2023-02-04 0:07 ` Trond Myklebust
2023-02-04 0:15 ` Hugh Dickins
2023-02-04 0:59 ` Trond Myklebust
2023-02-04 11:07 ` Thorsten Leemhuis
2023-02-04 13:15 ` Benjamin Coddington
2023-02-04 16:52 ` Trond Myklebust
2023-02-04 20:44 ` Benjamin Coddington
2023-02-05 11:24 ` Jeff Layton
2023-02-05 16:11 ` Benjamin Coddington
2023-02-01 15:11 ` Chuck Lever III
2023-02-03 12:39 ` Linux kernel regression tracking (#adding)
2023-02-21 14:58 ` Linux regression tracking #update (Thorsten Leemhuis) [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=34432a13-f809-b1a7-e737-e5646880da5d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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 NNTP newsgroup(s).