action #131483
closedcoordination #123583: [epic] Agama auto-installation
agama auto tests don't die on failure
Description
Observation¶
The agama auto tests for agama-live.x86_64-2.1.0-ALP-Build2.46.iso currently fail because on product selection, tumbleweed is missing. The issue is that the auto module failure should stop the test, but the rest of the modules run. In autoinst-log.txt :
......
[2023-06-27T09:37:28.918297+02:00] [info] [pid:31049] ::: basetest::runtest: # Test died: no candidate needle with tag(s) 'agama-main-page' matched
[2023-06-27T09:37:28.923163+02:00] [debug] [pid:31049] lib/yam/agama/agama_base.pm:23 called testapi::select_console
[2023-06-27T09:37:28.923289+02:00] [debug] [pid:31049] <<< testapi::select_console(testapi_console="root-console")
[2023-06-27T09:37:29.337002+02:00] [debug] [pid:31049] activate_console, console: root-console, type: console
[2023-06-27T09:37:29.337589+02:00] [debug] [pid:31049] lib/yam/agama/agama_base.pm:23 called testapi::select_console -> lib/susedistribution.pm:826 called testapi::wait_still_screen
...
We should check if the lib/yam/agama/agama_base.pm post_fail_hook is properly written and what causes this "proceed on failure" phenomenon.
Tips:
- Try to run the test with _SKIP_POST_FAIL_HOOKS=1 to see if this is the issue.
- If there is no aparent reason add a flag for the test to die on failure (DIE_ON_FAIL=1)
More auto tests in Development agama job group
openQA test in scenario alp-agama-2.1-staging-agama-live-default-x86_64-agama_auto_tumbleweed@64bit-2G fails in
auto
Test suite description¶
Auto installation of Tumbleweed on ALP Agama using .sh format
Reproducible¶
Fails since (at least) Build 2.26
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by syrianidou_sofia over 1 year ago
- Project changed from openQA Tests (public) to qe-yam
- Category deleted (
Bugs in existing tests) - Target version set to Current
Updated by JERiveraMoya over 1 year ago
- Priority changed from Normal to High
- Parent task set to #123583
Updated by coolgw over 1 year ago
- Status changed from Workable to In Progress
- Assignee set to coolgw
Updated by coolgw over 1 year ago
I think we can set milestone => 1 to block the test case for continue run.
Updated by coolgw over 1 year ago
Updated by JERiveraMoya over 1 year ago
- Status changed from In Progress to Resolved