Project

General

Profile

action #113348

[timeboxed:2h] OBS checks fail os-autoinst test "Calling 'isotovideo --help' returns exit code 0" from t/44-scripts.t but only on aarch64? -- initial investigation of "--help" route size:S

Added by okurz about 1 month ago. Updated about 1 month ago.

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

0%

Estimated time:
Difficulty:

Description

Motivation

We don't know what is going on with #113141

Suggestions

  • Check the "--help" route of isotovideo how that could return something else than 0, maybe some background processes? Check process tree?
  • Fix the issue or update #113141 with more specific insights what needs to be done

Related issues

Copied from openQA Project - action #113141: [sporadic] OBS checks fail os-autoinst test "Calling 'isotovideo --help' returns exit code 0" from t/44-scripts.t but only on aarch64?Resolved2022-07-01

History

#1 Updated by okurz about 1 month ago

  • Copied from action #113141: [sporadic] OBS checks fail os-autoinst test "Calling 'isotovideo --help' returns exit code 0" from t/44-scripts.t but only on aarch64? added

#2 Updated by okurz about 1 month ago

  • Subject changed from [timeboxed:2h] OBS checks fail os-autoinst test "Calling 'isotovideo --help' returns exit code 0" from t/44-scripts.t but only on aarch64? -- initial investigation of "--help" route to [timeboxed:2h] OBS checks fail os-autoinst test "Calling 'isotovideo --help' returns exit code 0" from t/44-scripts.t but only on aarch64? -- initial investigation of "--help" route size:S
  • Description updated (diff)
  • Status changed from New to Workable

#3 Updated by tinita about 1 month ago

  • Status changed from Workable to In Progress
  • Assignee set to tinita

The exit code is 124, and since the command is called with timeout 3, it's likely, that it just runs into the timeout.
Given that we often see non-os-autoinst related issues in the aarch64 builds, not sure if we can do much about it except increasing the timeout on this platform.

#4 Updated by tinita about 1 month ago

  • Status changed from In Progress to Feedback

I ran isotovideo in a loop on OBS aarch64, and it's not uncommon that the runtime goes up to 1.6s.
So I can easily imagine that on an especially slow build it goes beyond the 3 seconds.

I would say we increase the timeout per script to, say, 8s.

It would also be possible to do this only for aarch64, e.g. if $Config{archname} =~ m/aarch64/ but maybe that is overkill.
We have the overall OpenQA::Test::TimeLimit as a fallback anyway.

#5 Updated by tinita about 1 month ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF