netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: netdev@vger.kernel.org, MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [TEST] Flake report
Date: Thu, 30 May 2024 10:41:23 -0700	[thread overview]
Message-ID: <20240530104123.72ab528b@kernel.org> (raw)
In-Reply-To: <7e443c56-129e-4421-8dd8-adb57e9e6193@kernel.org>

On Thu, 30 May 2024 19:35:56 +0200 Matthieu Baerts wrote:
> > Yes, we need to find a solution for that. It is not as unstable on our
> > side [1]. We will look at that next week. If we cannot find a solution
> > quickly, we will skip the flaky subtests to stop the noise while
> > continuing to investigate.  
> Now that the flaky MPTCP subtests results have been ignored, the results
> look better:
> 
>   https://netdev.bots.linux.dev/flakes.html?br-cnt=88&tn-needle=mptcp
> 
> Do you think we could also stop ignoring them on NIPA side?

Thanks for take care of it, done!

  reply	other threads:[~2024-05-30 17:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 23:09 [TEST] Flake report Jakub Kicinski
2024-05-10  3:24 ` Hangbin Liu
2024-05-10  8:35 ` Florian Westphal
2024-05-10 14:47   ` Jakub Kicinski
2024-05-10 16:03     ` Jakub Kicinski
2024-05-10 16:41       ` Florian Westphal
2024-05-10 18:02         ` Jakub Kicinski
2024-05-11  0:14           ` Jakub Kicinski
2024-05-11  6:50             ` Florian Westphal
2024-05-10 14:28 ` Matthieu Baerts
2024-05-30 17:35   ` Matthieu Baerts
2024-05-30 17:41     ` Jakub Kicinski [this message]
2024-05-31  7:52       ` Matthieu Baerts
2024-05-10 14:45 ` Nikolay Aleksandrov
2024-05-11 13:27 ` Simon Horman
2024-05-14 13:52   ` Aaron Conole
2024-05-13 11:58 ` Davide Caratti
2024-05-13 16:52 ` Petr Machata
2024-05-14 13:43   ` Jakub Kicinski
2024-05-21 16:29   ` Petr Machata

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=20240530104123.72ab528b@kernel.org \
    --to=kuba@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.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).