action #56636
closed[functional][u] test fails in keymap_or_locale - No dmesg logs uploaded on post_fail_hook
0%
Description
Observation¶
No dmesg logs uploaded on post_fail_hook
This is due to opensusebasetest not calling export_logs method in the post fail hook and keymap_or_locale test, lacking a post_fail_hook implementation on it's own.
Acceptance criteria¶
- AC: keymap_or_locale upload at least dmesg on post_fail_hook
Tasks¶
- Add a post_fail_hook override that calls export_logs_basic and then calls the parent class's post fail hook
- BONUS: rename lib/local.pm to lib/localebasetest.pm (To ensure consistency across base tests modules)
sub post_fail_hook {
my ($self) = shift;
select_console('log-console');
$self->SUPER::post_fail_hook;
$self->export_logs_basic;
}
Reproducible¶
- In scenario sle-12-SP5-Server-DVD-x86_64-gnome@64bit
- It fails sporadically
- Example of Build 0307
Further details¶
Always latest result in this scenario: latest
Updated by SLindoMansilla over 4 years ago
- Status changed from New to Workable
- Priority changed from High to Normal
- Target version set to Milestone 28
- Estimated time set to 42.00 h
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: default@64bit-ipmi
https://openqa.suse.de/tests/3418731
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by maritawerner over 4 years ago
What is the status here? We are almost at GMC? Can we get that fixed?
Updated by SLindoMansilla over 4 years ago
- Priority changed from Normal to Urgent
Updated by zluo over 4 years ago
- Assignee set to zluo
- Priority changed from Urgent to High
take over and check the status for now:
bsc#1126782 has been mentioned for this issue.
Updated by zluo over 4 years ago
https://openqa.suse.de/tests/3485166#next_previous shows that we don't have this issue since about 30 days and I think this is related to the product issue with cpu softlock reported in mentioned bsc#1126782.
Of course I can add post_fail_hook in test module for exporting logs, but I don't think this will solve the issue coming from product. Anyway I will add post_fail_hook.
Updated by zluo over 4 years ago
- Status changed from Workable to Feedback
verification test: http://f40.suse.de/tests/5167#downloads
PR created:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8726
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: default@64bit-ipmi
https://openqa.suse.de/tests/3507584
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: default@64bit-ipmi
https://openqa.suse.de/tests/3577831
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed