MPTCP Linux Development
 help / color / mirror / Atom feed
* CI: packetdrill failures with debug mode are now ignored
@ 2026-05-27  6:59 Matthieu Baerts
  0 siblings, 0 replies; only message in thread
From: Matthieu Baerts @ 2026-05-27  6:59 UTC (permalink / raw)
  To: MPTCP Linux

Hello,

Packetdrill tests executed on a kernel built with a debug kernel config
are frequently failing due to various timing related issues. When
executed in this debug mode, the most important is to check if they
didn't cause "critical" issues.

It looks like these tests are more flaky with the more recent kernels,
which might indicate that some kernel debug config might now cause
executions to be even slower. I think it is better to ignore these
results, and only look for kernel calltraces, than spending a lot of
time trying to have these tests passing in very slow environments: this
is similar to what is done with the TCP packetdrill tests in the kernel
selftests.

Note that here, the failures will still be marked as IGNORE: so they
will still be recorded and appeared in the logs and on the "flakes" webpage:

  https://ci-results.mptcp.dev/flakes.html

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2026-05-27  6:59 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-27  6:59 CI: packetdrill failures with debug mode are now ignored Matthieu Baerts

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox