action #67408
closed[qem][qe-core] [evolution] test fails in evolution_smoke
Added by dzedro almost 4 years ago. Updated 12 months ago.
100%
Description
Observation¶
openQA test in scenario sle-15-SP2-Online-x86_64-wayland-desktopapps-message@64bit-virtio-vga fails in
evolution_smoke
Test suite description¶
smoke test often doesn't look up details of nooop_test3@aim.com email. https://openqa.suse.de/tests/4251958#step/evolution_smoke/13
I tried to do it in loop, but it does not help. http://10.100.12.155/tests/15936#step/evolution_smoke/56
Reproducible¶
Fails since (at least) Build 201.1
Expected result¶
Last good: 197.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dzedro almost 4 years ago
- Status changed from New to In Progress
- Assignee set to dzedro
Updated by dzedro almost 4 years ago
- Related to action #65169: [qam] [evolution] test fails in evolution_mail_imap added
Updated by dzedro almost 4 years ago
- Status changed from In Progress to New
- Assignee deleted (
dzedro)
Updated by dzedro almost 4 years ago
This issue was not about failure, but about soft fail which I implemented to avoid failure.
Updated by okurz almost 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: x11-desktopapps-message@64bit-2gbram
https://openqa.suse.de/tests/4342658
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 almost 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: x11-desktopapps-message@64bit-2gbram
https://openqa.suse.de/tests/4342658
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 dzedro almost 4 years ago
@okurz any idea why bot updated this poo# with 2 months old softfail ?
Updated by openqa_review over 3 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: x11-desktopapps-message@64bit-2gbram
https://openqa.suse.de/tests/4342658
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 openqa_review over 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/4637850
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 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/4816877
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 GraceWang over 3 years ago
dzedro wrote:
This issue was not about failure, but about soft fail which I implemented to avoid failure.
@dzedro
In fact, this issue was not resolved 100% and a soft fail was added to handle possible failure.
Please correct me if my understanding is not correct.
In SLE15SP3, this test suite only passed 2 times with all the other results (more than 20) go to soft fail.
Is there a way to resolve this issue without soft fail?
Updated by dzedro over 3 years ago
In fact, this issue does exist to document the failure and as reason for soft_fail, which does avoid failing test.
I can change this to work only for maintenance and you can have fun with failures and continue to blindly restart the test.
I don't know the reason why it is failing or how to debug it, maybe replace nooop_test3@aim.com with something else, maybe local email address.
Updated by okurz over 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/4922403
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 3 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: qam-mail-evolution
https://openqa.suse.de/tests/5034412
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 3 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: qam-mail-evolution
https://openqa.suse.de/tests/5125172
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 3 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: qam-regression-message
https://openqa.suse.de/tests/5190827
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 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5217869
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 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5287161
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 about 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5428752
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 about 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5478875
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 openqa_review about 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/5647241
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 about 3 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: x11-desktopapps-message@64bit-2gbram
https://openqa.suse.de/tests/5750482
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 about 3 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: x11-desktopapps-message@64bit-2gbram
https://openqa.suse.de/tests/5815624
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 about 3 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: x11-desktopapps-message@64bit-2gbram
https://openqa.suse.de/tests/5903880
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 almost 3 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: x11-desktopapps-message@64bit-2gbram
https://openqa.suse.de/tests/5990745
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 almost 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/6037440
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 almost 3 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: qam-regression-message
https://openqa.suse.de/tests/6226964
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 openqa_review almost 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/6037440
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 almost 3 years ago
- Subject changed from [qam] [evolution] test fails in evolution_smoke to [qam][qe-core] [evolution] test fails in evolution_smoke
- Status changed from Resolved to Feedback
^
Updated by openqa_review almost 3 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: wayland-desktopapps-message
https://openqa.suse.de/tests/6037440
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" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by mgrifalconi over 2 years ago
- Status changed from Feedback to Workable
Hello all, now it is failing all the time on 15-SP2 https://openqa.suse.de/tests/6786004#next_previous
Updated by martinsmac over 2 years ago
Hello all, now it is failing all the time on 15-SP3
https://openqa.suse.de/tests/6788950#step/evolution_smoke/21
Updated by tjyrinki_suse over 2 years ago
- Subject changed from [qam][qe-core] [evolution] test fails in evolution_smoke to [qem][qe-core] [evolution] test fails in evolution_smoke
- Priority changed from Normal to High
- Start date deleted (
2020-05-28)
This still seems a current topic indeed.
Note it does not fail always here at https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit-virtio-vga&test=wayland-desktopapps-message&version=15-SP2#next_previous
Updated by dzedro over 2 years ago
- Status changed from Workable to In Progress
- Assignee set to dzedro
Updated by dzedro over 2 years ago
- Status changed from In Progress to Blocked
The auth of nooops_test3@aim.com does not work in evolution, no idea why. I tried to login via web and that does work.
I reported https://bugzilla.suse.com/show_bug.cgi?id=1189513
Updated by dzedro over 2 years ago
- Status changed from Blocked to In Progress
Updated by dzedro over 2 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Updated by openqa_review over 2 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: wayland-desktopapps-message
https://openqa.suse.de/tests/7212211
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review over 2 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: qam-regression-message
https://openqa.suse.de/tests/7388152
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review over 2 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: qam-regression-message
https://openqa.suse.de/tests/7642709
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review about 2 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: wayland-desktopapps-message
https://openqa.suse.de/tests/8181085
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review over 1 year ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam-regression-message
https://openqa.suse.de/tests/9410708
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 388 days if nothing changes in this ticket.
Updated by slo-gin over 1 year ago
This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin over 1 year ago
This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by slo-gin over 1 year ago
This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by openqa_review over 1 year ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam-regression-message
https://openqa.suse.de/tests/10154093
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" or "EOL" (End-of-Life)
- 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.
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam-regression-message
https://openqa.suse.de/tests/10305686
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.
Updated by slo-gin about 1 year ago
This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by openqa_review about 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: wayland-desktopapps-message
https://openqa.suse.de/tests/10848566
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" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 116 days if nothing changes in this ticket.
Updated by mgrifalconi 12 months ago
- Status changed from Feedback to Workable
- Priority changed from High to Normal
This ticket is getting referenced by softfailures and cannot be resolved. We should decide if is worth to fix the softfailure or just keep the workaround without the softfailure tag to avoid this issue being opened over and over.
Updated by okurz 12 months ago
In general please do not use soft-failure reference to progress tickets only to product issues, i.e. bugzilla tickets. Reasoning: Consumers of the information commonly want to know if the product is affected by noteworthy bugs, everything else is just the test not being able to provide conclusive results regarding product quality. So a soft-fail reference to a test issue recorded in an open ticket is just as good as passing the test or excluding the affected test module or not running the test at all while the ticket is still open.