skip_by_date shows MTU tests as passing when we believe they should be failing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Committed
|
Medium
|
Unassigned |
Bug Description
e.g. in https:/
09:16:36 =======
09:16:36 ERROR: test suite for <class 'vmtests.
09:16:36 -------
09:16:36 Traceback (most recent call last):
09:16:36 File "/usr/lib/
09:16:36 self.setUp()
09:16:36 File "/usr/lib/
09:16:36 self.setupConte
09:16:36 File "/usr/lib/
09:16:36 super(NoSharedF
09:16:36 File "/usr/lib/
09:16:36 try_run(context, names)
09:16:36 File "/usr/lib/
09:16:36 return func()
09:16:36 File "/var/lib/
09:16:36 raise RuntimeError(msg)
09:16:36 RuntimeError: skip_by_
Related branches
- Dan Watkins (community): Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 42 lines (+6/-6)2 files modifiedtests/vmtests/test_network_ipv6_vlan.py (+2/-2)
tests/vmtests/test_network_vlan.py (+4/-4)
Changed in curtin: | |
importance: | Undecided → Medium |
status: | New → Triaged |
I've sorted this out. Once the skip_by_date fixby date has passed, we invoke the test; in this case the test looked like this:
def test_ip_ output( self):
pass
Which passes; but without actually running the test.
What we need to do instead is:
def test_ip_ output( self): ).test_ ip_output( )
super(