test_systemd_fsck_with_plymouth_failure passes but marked expected failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Medium
|
Dan Streetman | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Won't Fix
|
Medium
|
Unassigned | ||
Cosmic |
Won't Fix
|
Medium
|
Unassigned | ||
Disco |
Won't Fix
|
Medium
|
Unassigned | ||
Eoan |
Fix Released
|
Medium
|
Dan Streetman |
Bug Description
[impact]
this test case was marked as expected failure in the past to try to ignore failures, but it now passes and so causes autopkgtest failures.
[test case]
run autopkgtest and check for the 'test_systemd_
test_systemd_
Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... bash: line 1: 786 Killed /tmp/autopkgtes
autopkgtest [16:47:57]: test process requested reboot with marker test_systemd_
Connection to 10.44.40.6 closed by remote host.
autopkgtest-
test_systemd_
Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... unexpected success
-------
Ran 1 test in 17.952s
FAILED (unexpected successes=1)
[regression potential]
low; test case expectation fix only.
Changed in systemd (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Cosmic): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Disco): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Eoan): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Cosmic): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Disco): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Eoan): | |
importance: | Undecided → Medium |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Disco): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Cosmic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Bionic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Xenial): | |
status: | New → Invalid |
Changed in systemd (Ubuntu Eoan): | |
status: | In Progress → Fix Committed |
Changed in systemd (Ubuntu Disco): | |
assignee: | Dan Streetman (ddstreet) → nobody |
Changed in systemd (Ubuntu Cosmic): | |
assignee: | Dan Streetman (ddstreet) → nobody |
Changed in systemd (Ubuntu Bionic): | |
assignee: | Dan Streetman (ddstreet) → nobody |
Changed in systemd (Ubuntu Disco): | |
status: | In Progress → Won't Fix |
Changed in systemd (Ubuntu Cosmic): | |
status: | In Progress → Triaged |
Changed in systemd (Ubuntu Bionic): | |
status: | In Progress → Won't Fix |
Changed in systemd (Ubuntu Cosmic): | |
status: | Triaged → Won't Fix |
"and so causes autopkgtest failures." is not true.
From http:// autopkgtest. ubuntu. com/packages/ systemd/ bionic/ amd64 /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- bionic/ bionic/ amd64/s/ systemd/ 20190529_ 090547_ 1f40a@/ log.gz
E.g. https:/
Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... unexpected success
FAILED (unexpected successes=1)
autopkgtest [09:05:38]: test systemd-fsckd: ------- ------- ------- --]
systemd-fsckd PASS
Note systemd-fsckd only fails on failures & errors, and passed with unexpected successes: failures) != 0 or len(result.errors) != 0:
if len(result.
return_code = 1
I also wonder what has changed to make this test case reliable, in the past it used to be flakey, that's why i switched it to expectedfailure. I guess it's ok to reenable this in devel.
I see no need to reenable it in stable series. It has a regression potential, since it used to be flakey, it may start to be flakey again blocking SRU migrations.