autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there

Bug #1754472 reported by Christian Ehrhardt 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Opinion
Undecided
Unassigned

Bug Description

The test really seems to be triggered all of the time to resolve a flaky test.
That is just not worth the test.
But it provides goo coverage, so an override in britney would loose all that.

Lets skip the offending test on the arch it is known to be flaky (s390x).

Tags: patch
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

(untested) debdiff as suggestion.
I think this is trivial and will make the other tests more meaningful as a flaky test is more or less worth nothing (and consumed time on CI and of people).

tags: added: patch
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

That's not what I meant.

The test is valid, and on s390x, one consistently fails to run fsckd right.

I have already included a few overrides in bionic, where it is valid for fsckd to enter error state, as long as it does not block boot.

what release are you seeing this?

what you are saying here, is that fsck support on boot is broken on s390x, and that we do not care about it.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

This is outdated, lets close it in favor of focusing on new/recent issues.

Changed in systemd (Ubuntu):
status: New → Invalid
status: Invalid → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.