All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Taehee Yoo <ap420073@gmail.com>
Cc: netdev@vger.kernel.org
Subject: [TEST] amt.sh flaking
Date: Mon, 5 Jan 2026 18:07:12 -0800	[thread overview]
Message-ID: <20260105180712.46da1eb4@kernel.org> (raw)

Hi Taehee!

After migration to netdev foundation machines the amt.sh test has
gotten a bit more flaky:

https://netdev.bots.linux.dev/contest.html?test=amt-sh

In fact it's the second most flaky test we have after txtimestamp.sh.

All the failures are on non-debug kernels, and look like this:

TAP version 13
1..1
# timeout set to 3600
# selftests: net: amt.sh
# 0.26 [+0.26] TEST: amt discovery                                                 [ OK ]
# 15.27 [+15.01] 2026/01/05 19:33:27 socat[4075] W exiting on signal 15
# 15.28 [+0.01] TEST: IPv4 amt multicast forwarding                                 [FAIL]
# 17.30 [+2.02] TEST: IPv6 amt multicast forwarding                                 [ OK ]
# 17.30 [+0.00] TEST: IPv4 amt traffic forwarding torture               ..........  [ OK ]
# 19.48 [+2.18] TEST: IPv6 amt traffic forwarding torture               ..........  [ OK ]
# 26.71 [+7.22] Some tests failed.
not ok 1 selftests: net: amt.sh # exit=1

FWIW the new setup is based on Fedora 43 with:

# cat /etc/systemd/network/99-default.link
[Match]
OriginalName=*

[Link]
NamePolicy=keep kernel database onboard slot path
AlternativeNamesPolicy=database onboard slot path mac
MACAddressPolicy=none

             reply	other threads:[~2026-01-06  2:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06  2:07 Jakub Kicinski [this message]
2026-01-06 11:52 ` [TEST] amt.sh flaking Taehee Yoo
2026-01-14 11:55   ` Taehee Yoo
2026-01-15  2:45     ` Jakub Kicinski

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=20260105180712.46da1eb4@kernel.org \
    --to=kuba@kernel.org \
    --cc=ap420073@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.