Actions
action #178186
closedcoordination #154768: [saga][epic][ux] State-of-art user experience for openQA
coordination #154771: [epic] Improved test developer user experience
[sporadic] Failing OBS package check t/12_mocked_container.t for perl-Mojo-IOLoop-ReadWriteProcess on aarch64 size:S
Start date:
2025-03-03
Due date:
% Done:
0%
Estimated time:
Description
Observation¶
[ 100s]
[ 100s] # Failed test 'procs interface contains the added pids'
[ 100s] # at t/12_mocked_container.t line 37.
[ 100s] # got: ''
[ 100s] # expected: '1684
[ 100s] # '
[ 100s] #
[ 100s]
[ 100s] # Failed test 'Parent contains pid 1684'
[ 100s] # at t/12_mocked_container.t line 41.
[ 131s] # Looks like you failed 2 tests of 43.
[ 131s]
[ 131s] # Failed test 'container_3'
[ 131s] # at t/12_mocked_container.t line 258.
[ 131s] # Looks like you failed 1 test of 3.
[ 131s] t/12_mocked_container.t ..
[ 131s] Dubious, test returned 1 (wstat 256, 0x100)
[ 131s] Failed 1/3 subtests
Acceptance Criteria¶
AC1: OBS CI is passing consistently on aarch64 as well as other others
AC1: GitHub CI is passing on all archs
Suggestions¶
- Mitigate by removing the check based on architecture
- Be aware about #176148
- Consider reporting an upstream issue in https://github.com/openSUSE/Mojo-IOLoop-ReadWriteProcess/ but be aware that it is mostly us anyway that would need to fix such issues
- Consider workarounds within the test module
- Fix the root cause
- Ensure stability within multi-arch OBS checks
- Confirm if this also affects GitHub CI e.g. by proposing a trivial PR and checking the result
Actions