From: Jakub Kicinski <kuba@kernel.org>
To: Victor Nogueira <victor@mojatatu.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
kernel@mojatatu.com, pctammela@mojatatu.com
Subject: Re: [PATCH net-next] selftests: tc-testing: add mirred to block tdc tests
Date: Sun, 4 Feb 2024 08:33:25 -0800 [thread overview]
Message-ID: <20240204083325.41947dbd@kernel.org> (raw)
In-Reply-To: <b45bdefe-ee3b-4a07-a397-0b2f87ca56d3@mojatatu.com>
On Sat, 3 Feb 2024 17:15:32 -0300 Victor Nogueira wrote:
> > I think this breaks the TDC runner.
> > I'll toss it from patchwork, I can revive it when TDC is fixed (or you
> > tell me that I'm wrong).
>
> Oh, I think you caught an issue with the process.
> The executor was using the release iproute2 instead of iproute2-next,
> which I tested on. I'm wondering if other tests in nipa are using
> iproute2-next or release iproute2. The issue only arises if you have
> patches in net-next that are not in the release iproute2. We will fix
> the executor shortly.
We merge iproute2 into iprout2-next locally and build the combined
thing, FWIW. I haven't solved the problem of pending patches, yet,
tho :( If the iproute2-next patches are just on the list but not
merged the new tests will fail.
next prev parent reply other threads:[~2024-02-04 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 2:07 [PATCH net-next] selftests: tc-testing: add mirred to block tdc tests Victor Nogueira
2024-02-03 5:00 ` Jakub Kicinski
2024-02-03 20:15 ` Victor Nogueira
2024-02-04 16:33 ` Jakub Kicinski [this message]
2024-02-05 16:28 ` Victor Nogueira
2024-02-06 15:59 ` Jakub Kicinski
2024-02-28 16:49 ` Naresh Kamboju
2024-02-28 17:35 ` Victor Nogueira
2024-02-28 20:35 ` Naresh Kamboju
2024-02-09 20:40 ` patchwork-bot+netdevbpf
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=20240204083325.41947dbd@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=kernel@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=victor@mojatatu.com \
--cc=xiyou.wangcong@gmail.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 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.