action #43040
closed[functional][opensuse][u] test fails in gnucash - New behavior, test needs to be fixed
0%
Description
Observation¶
New behavior, test needs to be fixed.
gnucash-3.3-1.1 now shows a welcome popup that needs to be handled
Reproducible¶
Fails since Build 20181025
Scenarios:¶
On x86_64: openSUSE Tumbleweed build 20181025
On aarch64: openSUSE Tumbleweed AArch64 build 20181025
Expected result¶
Last good example: opensuse-Tumbleweed-DVD-aarch64-Build20181018-lxde@aarch64
Further details¶
Always latest link: opensuse-Tumbleweed-DVD-aarch64-Build20181026-lxde@aarch64#latest
Updated by SLindoMansilla over 5 years ago
- Subject changed from [functional][opensuse] test fails in gnucash - New behavior, test needs to be fixed to [functional][opensuse][u] test fails in gnucash - New behavior, test needs to be fixed
Updated by okurz over 5 years ago
- Status changed from New to In Progress
- Assignee set to okurz
- Priority changed from Normal to High
- Target version set to Milestone 20
As gnucash becomes annoying too many test reviewers they tend to ignore corresponding test results. This should be handled with urgency and is probably not so hard to do. There is a new TW snapshot on x86_64 which is easier to investigate for many people so I will monitor https://openqa.opensuse.org/tests/783612 and alike first to see if we can observe the problem there as well.
Updated by SLindoMansilla over 5 years ago
- Blocks action #42443: [functional][u][sporadic] test fails in gnucash of openSUSE upgrade scenario, maybe sporadic? performance related? added
Updated by dimstar over 5 years ago
okurz wrote:
As gnucash becomes annoying too many test reviewers they tend to ignore corresponding test results.
This is simply the first snapshot with gnucash version 3.3
But imho, we should probably move gnucash to the GNOME/KDE-extra tests; there is really no reason to test this application in every scenario (just to make it less painful also - and especially not having it in the GNOME test, where the disk image is being used after for the further tests)
Updated by dimstar over 5 years ago
dimstar wrote:
But imho, we should probably move gnucash to the GNOME/KDE-extra tests; there is really no reason to test this application in every scenario (just to make it less painful also - and especially not having it in the GNOME test, where the disk image is being used after for the further tests)
This last part is proposed in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6077 - not fixing this ticket, but making gnucash less of an annoyance
Updated by okurz over 5 years ago
dimstar wrote:
This last part is proposed in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6077
merged
Updated by okurz over 5 years ago
the next part can simply be conducted by cloning extra_tests_on_gnome and adjusting the test flow and needles
Updated by okurz over 5 years ago
- Status changed from In Progress to Feedback
Updated by okurz over 5 years ago
PRs merged and deployed.
- extra_tests_on_gnome currently running
- extra_tests_on_kde probably needs needle adjustements
- extra_tests_on_xfce the same
openqa_clone_job_o3 --skip-chained-deps 784083 _GROUP=0 BUILD=20181029:poo43040 TEST=extra_tests_on_kde_okurz_poo43040 INCLUDE_MODULES=boot_to_desktop,gnucash _SKIP_POST_FAIL_HOOKS=1
openqa_clone_job_o3 --skip-chained-deps 784084 _GROUP=0 BUILD=20181029:poo43040 TEST=extra_tests_on_xfce_okurz_poo43040 INCLUDE_MODULES=boot_to_desktop,gnucash _SKIP_POST_FAIL_HOOKS=1
-> https://openqa.opensuse.org/t784424 and https://openqa.opensuse.org/t784425
Updated by okurz over 5 years ago
https://openqa.opensuse.org/tests/784430#step/gnucash/20 is unfortunate, the tip window shows up after the assistant has been closed. Reproducing locally again and adjusting test code.
https://openqa.opensuse.org/tests/784441
Someone wrote: "As far as I can see it is missed, see https://openqa.opensuse.org/tests/784430/file/video.ogv#t=7.23,7.28" . That's good so maybe I can just create the needle afterwards and it will pick it up.
I missed the _ in the above clone job call so all jobs ended up in the validation job group. Fixed that with
for i in $(openqa_client_o3 --json-output jobs build=20181029:poo43040 | jq '.jobs | .[] | .id') ;do openqa_client_o3 jobs/$i put --json-data '{"group_id": 38}' ; done
https://openqa.opensuse.org/tests/784441 is the final validation on xfce, https://openqa.opensuse.org/tests/784448 the preliminary one on plasma, https://openqa.opensuse.org/tests/784449 triggered as final validation on plasma which passed as well.
Updated by okurz over 5 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: extra_tests_on_kde
https://openqa.opensuse.org/tests/792150