From: David Marchand <david.marchand@redhat.com>
To: dpdklab <dpdklab@iol.unh.edu>
Cc: dev <dev@dpdk.org>, ci@dpdk.org, Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-ci] [dpdk-dev] [PATCH 0/2] 21.05 fixes for OVS
Date: Fri, 7 May 2021 14:21:33 +0200 [thread overview]
Message-ID: <CAJFAV8xTdK2Sf9fNNnHV=PwY0J6Yid4+zcz+6DAOM2xFWjcBvA@mail.gmail.com> (raw)
In-Reply-To: <20210506151426.28202-1-david.marchand@redhat.com>
On Thu, May 6, 2021 at 5:15 PM David Marchand <david.marchand@redhat.com> wrote:
>
> Testing OVS build against 21.05-rc2 revealed some issues.
> Bits were also missing on OVS side, so for people interested, a
> rebased dpdk-latest OVS branch is available at:
> https://github.com/david-marchand/ovs/commits/dpdk-latest
I got failures for a "dynamic_config" job running on the Mellanox
server from the lab.
I don't see how my patches could break this.
Max segment number per MTU/TSO: 40
Switch name: 0000:05:00.0
Switch domain Id: 0
Switch Port Id: 65535
06/05/2021 14:03:20 TestDynamicConfig: set_up_all failed:
Traceback (most recent call last):
File "/home/jenkins/dts-func/framework/test_case.py", line 258, in
execute_setup_all
self.set_up_all()
File "tests/TestSuite_dynamic_config.py", line 93, in set_up_all
self.verify(ret.lower() == self.dest, "MAC address wrong")
File "/home/jenkins/dts-func/framework/test_case.py", line 169, in verify
raise VerifyFailure(description)
exception.VerifyFailure: 'MAC address wrong'
06/05/2021 14:03:20 dts:
TEST SUITE ENDED: TestDynamicConfig
The DTS code does not seem to have changed recently.
Is this test stable?
--
David Marchand
next parent reply other threads:[~2021-05-07 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210506151426.28202-1-david.marchand@redhat.com>
2021-05-07 12:21 ` David Marchand [this message]
2021-05-07 13:15 ` Aaron Conole
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='CAJFAV8xTdK2Sf9fNNnHV=PwY0J6Yid4+zcz+6DAOM2xFWjcBvA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
/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;
as well as URLs for NNTP newsgroup(s).