netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, Mat Martineau <martineau@kernel.org>,
	Geliang Tang <geliang@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: mptcp: lib: fix shellcheck errors
Date: Mon, 15 Jul 2024 09:44:25 -0700	[thread overview]
Message-ID: <20240715094425.73738ca0@kernel.org> (raw)
In-Reply-To: <7a1fea0c-1389-4867-aaec-0c0db01cb6c0@kernel.org>

On Mon, 15 Jul 2024 11:07:26 +0200 Matthieu Baerts wrote:
> > Speaking of MPTCP tests - I added the connect test to ignored today.
> > Too many failures :(  
> 
> Sorry for that, and thank you for having ignore it for the 'dbg' runner.
> 
> This sudden regression looks strange. Our CI didn't catch this issue so
> far. It is only happening with the debug kernel config.
> 
> Do you know if anything has changed recently -- around the 11th of July
> -- on NIPA's config side that is not documented? e.g. more jobs in
> parallel, new kernel config? I didn't see anything that could cause the
> new issues when looking at NIPA's git log and the CI change log sheet.

The usual suspect on Thursdays is that we pull in changes from Linus,
it'd be surprising if there were major changes there the week of the
release but maybe..

> I will try to reproduce the issue locally, maybe it is caused by a patch
> that is in patchwork, but not in net or net-next yet.

I was going to mention Kuniyuki's patch but you discovered it already :)

  reply	other threads:[~2024-07-15 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 10:00 [PATCH net-next] selftests: mptcp: lib: fix shellcheck errors Matthieu Baerts (NGI0)
2024-07-12 18:24 ` Simon Horman
2024-07-13 22:46 ` Jakub Kicinski
2024-07-15  9:07   ` Matthieu Baerts
2024-07-15 16:44     ` Jakub Kicinski [this message]
2024-07-13 22:50 ` patchwork-bot+netdevbpf

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=20240715094425.73738ca0@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=geliang@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.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 NNTP newsgroup(s).