Project

General

Profile

action #105061

[sporadic] os-autoinst: 29-backend-driver.t: Failed test 'log output for backend driver creation' size:S

Added by okurz 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Concrete Bugs
Target version:
Start date:
2022-01-19
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

https://build.opensuse.org/package/live_build_log/devel:openQA:TestGithub:OPR-1924/os-autoinst/openSUSE_15.3/x86_64 showed

[  206s] 3: #   Failed test 'log output for backend driver creation'
[  206s] 3: #   at ./29-backend-driver.t line 24.
[  206s] 3: # STDOUT & STDERR:
[  206s] 3: # hannel_in 20
[  206s] 3: # [0m
[  206s] 3: # don't match:
[  206s] 3: # (?^u:(Blocking SIGCHLD|channel_out))
[  206s] 3: # as expected
[  206s] 3: # Looks like you failed 1 test of 12.
[  206s] 3: [13:25:34] ./29-backend-driver.t .................... 
[  206s] 3: not ok 1 - log output for backend driver creation

I have seen this at least twice but AFAIR only in OBS checks

Acceptance criteria

  • AC1: 29-backend-driver.t doesn't fail in OBS checks

Suggestions

  • Just add t/29-backend-driver.t to the exclude list in dist/rpm/os-autoinst.spec

History

#1 Updated by cdywan 4 months ago

  • Subject changed from [sporadic] os-autoinst: 29-backend-driver.t: Failed test 'log output for backend driver creation' to [sporadic] os-autoinst: 29-backend-driver.t: Failed test 'log output for backend driver creation' size:S
  • Description updated (diff)
  • Status changed from New to Workable

#2 Updated by kraih 4 months ago

  • Assignee set to kraih

#4 Updated by kraih 4 months ago

  • Status changed from Workable to In Progress

#5 Updated by kraih 4 months ago

  • Status changed from In Progress to Resolved

#6 Updated by kraih 4 months ago

  • Status changed from Resolved to Feedback

#7 Updated by kraih 4 months ago

  • Status changed from Feedback to Resolved

#8 Updated by AdamWill 4 months ago

FWIW, I saw this in Fedora package builds a couple of times too.

#9 Updated by AdamWill 4 months ago

It's not really great to just keep disabling tests every time we hit a bug, of course. It's noticeable that we (both SUSE and Fedora) have had 07-commands.t disabled for two years in package builds for a similar reason:

https://progress.opensuse.org/issues/60755

maybe we should try and figure out what's going on with stderr/stdout capture in the package build environment? Is the capture itself going wrong? Or are unexpected additional messages being output on stderr/stdout that mess with the tests?

Also available in: Atom PDF