Project

General

Profile

action #42536

[functional][u] test fails in force_scheduled_tasks - "select_console 'root-console'" failed because of btrfs info message on the screen which should not be there but this very module should prevent further messages and therefore handle this gracefully

Added by okurz almost 2 years ago. Updated 7 months ago.

Status:
Rejected
Priority:
Normal
Category:
Bugs in existing tests
Target version:
Start date:
2018-10-16
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-15.1-DVD-x86_64-zdup-Leap-42.2-gnome@64bit-2G fails in
force_scheduled_tasks

Reproducible

Fails since (at least) Build 319.2 (current job)

Expected result

Last good: 318.2 (or more recent)

Suggestions

  • Try to not rely on "select_console" with the screen assertion afterwards but maybe instead if the first match fails press return multiple times and look for the screen again, at best with record_soft_failure to the bug (to be looked for on bugzilla.opensuse.org) about messages on the screen

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #43784: [functional][y][sporadic] test fails in yast2_snapper now reproducibly not exiting the "show differences" screenResolved2018-11-14

History

#1 Updated by okurz almost 2 years ago

  • Related to action #43784: [functional][y][sporadic] test fails in yast2_snapper now reproducibly not exiting the "show differences" screen added

#2 Updated by mloviska over 1 year ago

Unfortunately, the link from the description is not valid anymore.
Are we dealing with the same issue over here as well ? sle-15-SP1-Installer-DVD-aarch64-Build137.1-allpatterns@aarch64

[ 1100.462427] sysrq: SysRq : Show Blocked State
[ 1100.465545]   task                        PC stack   pid father
[ 1100.470162] btrfs           D    0  3665   3657 0x00000008
[ 1100.474166] Call trace:
[ 1100.476020]  __switch_to+0x9c/0xe0
[ 1100.478525]  __schedule+0x22c/0x850
[ 1100.481653]  schedule+0x2c/0x88
[ 1100.490250]  __scrub_blocked_if_needed+0x6c/0xb0 [btrfs]
[ 1100.494959]  scrub_pause_off+0x30/0x70 [btrfs]
[ 1100.499232]  scrub_stripe+0x69c/0xce0 [btrfs]
[ 1100.503061]  scrub_chunk+0x138/0x190 [btrfs]
[ 1100.506484]  scrub_enumerate_chunks+0x274/0x550 [btrfs]
[ 1100.513019]  btrfs_scrub_dev+0x1e8/0x488 [btrfs]
[ 1100.516827]  btrfs_ioctl+0x182c/0x21f0 [btrfs]
[ 1100.520053]  do_vfs_ioctl+0xb0/0x848
[ 1100.522697]  SyS_ioctl+0x8c/0xa8
[ 1100.525065]  el0_svc_naked+0x44/0x48

#3 Updated by okurz 8 months ago

recent related failure: https://openqa.opensuse.org/tests/1169532/

Created workaround needle to catch this: user-console-qgroup_scan_completed-poo42536-20200210

#4 Updated by okurz 7 months ago

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

This bug is still referenced in a failing openQA test: zdup-Leap-42.2-gnome@64bit_cirrus
https://openqa.opensuse.org/tests/1190581

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"
  3. The label in the openQA scenario is removed

#5 Updated by SLindoMansilla 7 months ago

  • Status changed from New to Rejected
  • Assignee set to SLindoMansilla

Not reproducible anymore for 3 months: https://openqa.opensuse.org/tests/1192161#next_previous

#6 Updated by okurz 7 months ago

An issue like this can reappear any time. You might have missed the suggestion in the subject line.

Also available in: Atom PDF