try to catch a boot loop after dnf system-upgrade reboot, if
we do, set the test to soft_fail and pass enforcing=0 to work
around it.
Details
Details
Run the upgrade_foo tests and see that they now soft
fail instead of hard failing (unless there are any other issues).
Run the upgrade_2_foo tests and make sure they still pass (i.e.
we don't erroneously soft fail them).
Diff Detail
Diff Detail
- Repository
- rOPENQATESTS os-autoinst-distri-fedora
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
staging is using this branch, and I've re-run the upgrade tests for today on it; see https://openqa.stg.fedoraproject.org/tests/overview?groupid=1&version=Rawhide&build=Fedora-Rawhide-20160629.n.0&distri=fedora .
Comment Actions
oh, and I should say, the reason to do this (rather than just let the tests keep failing) is we know about the bug and it seems better to work around it so we can check for *other* bugs, rather than continuing to fail on one we already know about.