Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Pedro Tammela <pctammela@mojatatu.com>, Netdev <netdev@vger.kernel.org>
Subject: Re: NIPA: TDC: delay the start
Date: Fri, 6 Nov 2026 09:24:41 -0800	[thread overview]
Message-ID: <20261106092441.00cf9765@kernel.org> (raw)
In-Reply-To: <6f0ee3c4-32b7-4422-b69d-c879c94262a7@kernel.org>

On Thu, 5 Nov 2026 11:43:27 +0100 Matthieu Baerts wrote:
> Hi Pedro,
> 
> I hope you are doing well.
> 
> I'm helping the netdev maintainers with the CI (NIPA), and lately, I
> noticed the 'tdc' runners were often marked as either "timeout" or
> "pending". It looks like this is because it missed the creation of the
> branch which can take more than 2 minutes for various reasons: PW access
> is slow, git push needs to be retried in a few seconds, etc.
> 
> I opened a PR to delay the start:
> 
>   https://github.com/p4tc-dev/tc-executor/pull/2
> 
> Another solution is to let the tdc* services running and doing the
> monitoring themselves. In other words, you need to remove
> "single_shot=true" from the config file. It might require you to update
> the NIPA repo you are using to get access to a bunch of fixes.

Keeps happening, I dropped TDC from required runners for now.

  reply	other threads:[~2026-11-06 17:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 10:43 NIPA: TDC: delay the start Matthieu Baerts
2026-11-06 17:24 ` Jakub Kicinski [this message]
2026-11-06 21:39   ` Jamal Hadi Salim
2026-11-09 16:58     ` Matthieu Baerts
2026-11-09 17:22       ` Jamal Hadi Salim
2026-11-09 17:31         ` Matthieu Baerts
2026-11-09 17:39           ` Victor Nogueira
2026-11-09 18:40             ` Matthieu Baerts
2026-11-09 18:49               ` Matthieu Baerts

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=20261106092441.00cf9765@kernel.org \
    --to=kuba@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pctammela@mojatatu.com \
    /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