Bug #12131

Step 'I double-click the Report an Error launcher on the desktop' sometimes fails

Added by anonym 2017-01-11 16:09:47 . Updated 2017-03-09 13:59:59 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_2.11
Start date:
2017-01-11
Due date:
% Done:

100%

Feature Branch:
test/12131-retry-report-an-error
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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.

Subtasks

History

#1 Updated by anonym 2017-01-11 16:10:25

  • Subject changed from Step äI double-click the Report an Error launcher on the desktop' sometimes fails to Step 'I double-click the Report an Error launcher on the desktop' sometimes fails

#2 Updated by anonym 2017-01-11 16:11:35

  • Description updated

#3 Updated by anonym 2017-01-11 18:38:11

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.

#4 Updated by intrigeri 2017-01-16 11:18:47

#5 Updated by anonym 2017-02-20 14:54:10

  • Status changed from Confirmed to In Progress

Applied in changeset commit:e2cf2896dbae20f66689e1e3c67202a2db319308.

#6 Updated by anonym 2017-02-20 18:44:05

  • 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

Instead of @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 2017-03-01 12:23:17

  • 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 test/12131-retry-report-an-error into 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.

intrigeri, can you do a post-merge review of test/12131-retry-report-an-error? That is commits:

  • commit:e2cf2896db Test suite: add retry magic for lost click.
  • commit:a7fb05c152 Test suite: Dogtailify step.
  • commit:3bc868968f Test suite: make force_new_tor_circuit() respect NEWNYM rate limiting.

#8 Updated by intrigeri 2017-03-02 07:41:57

  • 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 commit: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?

#9 Updated by anonym 2017-03-02 08:10:47

  • Assignee changed from anonym to intrigeri
  • QA Check changed from Dev Needed to Ready for QA

I did s/rate/interval/ in commit:f70dca933a. Good enough?

#10 Updated by intrigeri 2017-03-02 08:47:51

  • Status changed from In Progress to Fix committed
  • Assignee deleted (intrigeri)
  • % Done changed from 90 to 100
  • QA Check changed from Ready for QA to Pass

Yes!

#11 Updated by anonym 2017-03-09 13:59:59

  • Status changed from Fix committed to Resolved