action #18902
closed[qam]test fails in firefox_pdf - Timeout too low
100%
Description
Observation¶
openQA test in scenario sle-12-SP1-Desktop-DVD-Updates-x86_64-qam-regression-firefox@64bit fails in
firefox_pdf
The timeout should be increased from 90seconds to 120s or even more: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/x11regressiontest.pm#L462
This issue, doesn't happen always, but it seems to happen constantly.
Reproducible¶
Fails since (at least) Build 20170502-3
Expected result¶
Last good: 20170502-2 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz@suse.de over 7 years ago
On Tuesday, 2 May 2017 15:29:21 CEST you wrote:
[…]
Observation¶
openQA test in scenario
sle-12-SP1-Desktop-DVD-Updates-x86_64-qam-regression-firefox@64bit fails in
firefox_pdfThe timeout should be increased from 90seconds to 120s or even more:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/
x11regressiontest.pm#L462This issue, doesn't happen always, but it seems to happen constantly.
If you (QAM) think this is an acceptable performance regression or it can't be
fixed, why not directly do that change in the code and create a pull request?
Referencing a github pull request as "test issue" works the same as for
progress tickets. You can just paste the github pull request URL in a jobs
comment field
Updated by okurz almost 7 years ago
- Subject changed from test fails in firefox_pdf - Timeout too low to [qam]test fails in firefox_pdf - Timeout too low
- Assignee set to dasantiago
Hi, can you check the current situation?
Updated by dasantiago almost 7 years ago
- Status changed from New to Resolved
All the firefox_pdf tests that i saw where working correctly.
Marking as resolved.