Project

General

Profile

Actions
Copy link

action #158799

open

test fails in glibc_locale

Added by ggardet_arm 23 days ago. Updated 8 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2024-04-10
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos@aarch64_cpu_max-HD20G fails in
glibc_locale

Test fails on slow @cpu_max machine since the following code takes too long:

sub switch_user {
    enter_cmd("su - $testapi::username");
    validate_script_output('whoami', sub { m/$testapi::username/ });
}

Test suite description

Maintainer: fvogt, mnowak

Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64.

Reproducible

Fails since (at least) Build 20240213

Expected result

Last good: 20240212 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by openqa_review 8 days ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: jeos@
https://openqa.opensuse.org/tests/4102965#step/glibc_locale/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link

Also available in: Atom PDF