Netdev List
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Victor Nogueira <victor@mojatatu.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
	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 19:40:04 +0100	[thread overview]
Message-ID: <851b4466-3141-464e-810e-94befcf90286@kernel.org> (raw)
In-Reply-To: <CA+NMeC9TKz3a=8JYHavHRv2UcM4GxhhnqM9QzzVAu4gKSiz59A@mail.gmail.com>

Hi Victor,

On 09/11/2026 18:39, Victor Nogueira wrote:
> Hi Matthieu,
> 
> On Mon, Nov 9, 2026 at 2:31 PM Matthieu Baerts <matttbe@kernel.org> wrote:
>>
>> On 09/11/2026 18:22, Jamal Hadi Salim wrote:
>>> On Mon, Nov 9, 2026 at 11:58 AM Matthieu Baerts <matttbe@kernel.org> wrote:
>>>>
>>>> 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
>>>>>>> [...]
>>>>
>>>> Good idea, I just changed that!
>>>>
>>>> Please ping me when it is fixed, so I can re-enable the runner on NIPA's
>>>> side.
>>>
>>> @Victor Nogueira  is the one fixing it..
> 
> I applied the change Saturday and it's been running fine since then.

Ah good, thank you, I thought I had to wait because the PR was not merged.

> I think it's safe to re-enable now.

Just did!

Cheers,
Matt

  reply	other threads:[~2026-11-09 18:40 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
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 [this message]
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=851b4466-3141-464e-810e-94befcf90286@kernel.org \
    --to=matttbe@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pctammela@mojatatu.com \
    --cc=victor@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