From: Matthieu Baerts <matttbe@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Pedro Tammela <pctammela@mojatatu.com>,
Netdev <netdev@vger.kernel.org>
Subject: Re: NIPA: TDC: delay the start
Date: Mon, 9 Nov 2026 17:58:02 +0100 [thread overview]
Message-ID: <ef3ca6c4-57f4-44a7-b44e-f34e06dfb3dc@kernel.org> (raw)
In-Reply-To: <CAM0EoM=4fNFXaFUV1kh-H9Bdrt_K0yDsbOMJHWpgON2bG-GyEA@mail.gmail.com>
Hi Jamal,
Thank you for your reply!
On 06/11/2026 22:39, Jamal Hadi Salim wrote:
> ,
>
> On Fri, Nov 6, 2026 at 12:28 PM Jakub Kicinski <kuba@kernel.org> wrote:
>>
>> 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.
>
> This was an issue related to the indeterminate time it takes for the
> branch to show up after creation.
Just to put a bit more context, having no results from a runner means
the CI cannot validate whether the batch being tested was passing all
the tests or not. So we need to wait 3 more hours to get results. It's
not dramatic, but here it happens regularly, and it should be easy to fix.
> Matthieu, Victor responded to you; the overall proposal you made looks
> good. I don't know how we can fix this, but since Pedro is currently
> away we saw this mention by pure luck: Can we change the contact email
> address to hybris@mojatatu.ai? That way if you send an email there,
> one of several people will see it and respond.
Good idea, I just changed that!
Please ping me when it is fixed, so I can re-enable the runner on NIPA's
side.
Cheers,
Matt
next prev parent reply other threads:[~2026-11-09 16:58 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
2026-11-06 21:39 ` Jamal Hadi Salim
2026-11-09 16:58 ` Matthieu Baerts [this message]
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=ef3ca6c4-57f4-44a7-b44e-f34e06dfb3dc@kernel.org \
--to=matttbe@kernel.org \
--cc=jhs@mojatatu.com \
--cc=kuba@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