action #103422
Updated by okurz over 2 years ago
## Observation First seen on https://github.com/os-autoinst/os-autoinst/pull/1871#issuecomment-984670874: ``` 8: [11:23:53] ./12-bmwqemu.t ........................... ok 914 ms ( 0.01 usr 0.00 sys + 0.82 cusr 0.09 csys = 0.92 CPU) 8: 8: # Failed test 'Exit code appear in log' 8: # at ./13-osutils.t line 167. 8: # STDERR: 8: # [2021-12-02T11:23:54.401579Z] [debug] running `echo foo` 8: # [2021-12-02T11:23:54.405060Z] [debug] Command `echo foo` terminated with 1 8: # foo 8: # 8: # doesn't match: 8: # (?^u:terminated with 0) 8: # as expected 8: # Looks like you failed 1 test of 10. 8: 8: # Failed test 'run_diag' 8: # at ./13-osutils.t line 190. 8: # Looks like you failed 1 test of 9. 8: [11:23:54] ./13-osutils.t ........................... 8: Dubious, test returned 1 (wstat 256, 0x100) 8: Failed 1/9 subtests ``` I couldn't find another instance. What I did find was [another failure that didn't fail CI](https://github.com/os-autoinst/os-autoinst/pull/1789#issuecomment-984678259) in `14-isotovideo.t:128`. ## Acceptance criteria * **AC1:** Failure in 13-osutils.t fails CI * **AC2:** 13-osutils.t passes w/o failures ## Suggestions - Confirm when 13-osutils.t started failing - Fix 13-osutils.t - Compare if 14-isotovideo.t and maybe other tests generally don't fail CI - Ensure that the pipeline fails if any tests fail