DPDK dep8 tests failing on non supported platforms
Bug #1551158 reported by
Christian Ehrhardt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dpdk (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
While adding further tests we realized that DPDK tests would fail on non supported platforms.
While it makes perfect sense for them to fail, most involved people wondered why it even ran there.
Long story short: The dpdk package builds packages for all platforms like libdpdk-dev - therefore it's tests are tried to run on all platforms.
Now all the time the only thing avoiding this issue to be seen was that the tests had an "isolation-machine" restriction.
That accidentally limited the execution just to the supported i386 and amd64 for now.
When adding another Test which did not have that restrictions the issues started to show up.
Revision history for this message
| Christian Ehrhardt (paelzer) wrote | #1 |
| Changed in dpdk (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Christian Ehrhardt (paelzer) wrote | #2 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in dpdk (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
After discussing on #ubuntu-devel it was decided that the tests should guard themselves and skip the test if not appropriate.
Such specific HW need seems rare and there is no e.g. autopkgtest feature to limit Architectures.
Note: it was considered a "regression" because the fact that before we couldn't run it was not a "fault" of the Test (but of our environment). So when the new failing test landed it became a regression.