From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 700] dynamic_config is failing on Mellanox hardware
Date: Sun, 09 May 2021 07:12:50 +0000 [thread overview]
Message-ID: <bug-700-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=700
Bug ID: 700
Summary: dynamic_config is failing on Mellanox hardware
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: job scripts
Assignee: ci@dpdk.org
Reporter: alialnu@nvidia.com
CC: dpdklab@iol.unh.edu
Target Milestone: ---
The functional test (dynamic_config) is failing for many patches.
Failure:
"""
08/05/2021 05:40:53 TestDynamicConfig: set_up_all failed:
Traceback (most recent call last):
File "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 "framework/test_case.py", line 169, in verify
raise VerifyFailure(description)
exception.VerifyFailure: 'MAC address wrong'
"""
Most recent failures:
https://lab.dpdk.org/results/dashboard/patchsets/16991/
https://lab.dpdk.org/results/dashboard/patchsets/16990/
https://lab.dpdk.org/results/dashboard/patchsets/16989/
https://lab.dpdk.org/results/dashboard/patchsets/16988/
https://lab.dpdk.org/results/dashboard/patchsets/16982/
https://lab.dpdk.org/results/dashboard/patchsets/16987/
https://lab.dpdk.org/results/dashboard/patchsets/16955/
https://lab.dpdk.org/results/dashboard/patchsets/16955/
https://lab.dpdk.org/results/dashboard/patchsets/16991/
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-05-09 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 7:12 bugzilla [this message]
2021-05-19 16:35 ` bugzilla
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=bug-700-149@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@dpdk.org \
/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).