Bug #10288: Fix newly identified issues to make our test suite more robust and faster
Step 'I double-click the Report an Error launcher on the desktop' sometimes fails
The double click loses one click, so the launcher is only selected, not opened, so we fail in the next subsequent step by timing out waiting for the browser to start.
#3 Updated by anonym almost 3 years ago
Here's an example, if useful: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/675/
Relevant part of the log:
[...] [log] DOUBLE CLICK on (89,174) When I double-click the Report an Error launcher on the desktop # features/step_definitions/checks.rb:38 [... dogtail stuff looping ...] application = tree.root.application('"'"'Firefox'"'"') application.child('"'"'Tails - Hilfe & Support - Tor-Browser'"'"', roleName='"'"'frame'"'"')' >> '/tmp/tmp.OUcsE0TyWt' call returned: [3043, 0, "", ""] calling as amnesia: /usr/bin/python '/tmp/tmp.OUcsE0TyWt' Then the support documentation page opens in Tor Browser # features/step_definitions/checks.rb:131 try_for() timeout expired Last ignored exception was: ExecutionFailedInVM: Command failed: /usr/bin/python '/tmp/tmp.dbgDo9Cwqm' error code: 1 stderr: . <false> is not true. (Timeout::Error) [...]
A lost click downgrading the double-click to a single click indeed seems like the cause.
#6 Updated by anonym over 2 years ago
- Assignee set to anonym
- Target version set to Tails_2.11
- % Done changed from 0 to 30
- QA Check set to Dev Needed
- Feature Branch set to test/12131-retry-report-an-error
@fragile-tagging I tried for a fix. Given how frequently these scenarios fail, I say we merge it if we get five Jenkins runs without this failure.
#7 Updated by anonym over 2 years ago
- Status changed from In Progress to Fix committed
- Assignee changed from anonym to intrigeri
- % Done changed from 30 to 100
- QA Check changed from Dev Needed to Ready for QA
So apparently I had ff-merged
stable when I forked off
feature/12272-vagrant-offline-builds from it, and the latter branch was just merged, so this ticket's branch was merged by mistake. So, hopefully this branch is fine, which should immediately improve all test runs on Jenkins.
test/12131-retry-report-an-error? That is commits:
#8 Updated by intrigeri over 2 years ago
- Status changed from Fix committed to In Progress
- Assignee changed from intrigeri to anonym
- % Done changed from 100 to 90
- QA Check changed from Ready for QA to Dev Needed
Looks good, except the
rate variable introduced in 3bc868968f47c414bdb3e32d09df675fea5766b8 is not really a rate, right? The larger it gets, the slower newnyms are issued. Can you please find a better name for it?