Feature #11449

Decrease boot timeout in the test suite

Added by intrigeri 2016-05-19 10:09:34 . Updated 2016-11-15 18:23:33 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Test suite
Target version:
Tails_2.7
Start date:
2016-05-19
Due date:
% Done:

100%

Feature Branch:
test/11449-decrease-boot-timeout
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:
270

Description

Currently we wait up to 30 minutes:

  @screen.wait('TailsGreeter.png', 30*60)

… which makes the (failing) test suite runs on feature/stretch take many hours, because the Greeter fails to appear there.

AFAIK nobody runs the test suite in nested virtualization on slow hardware anymore, and even if they tried, I bet that lots of other things would be broken. IMO we should not bother trying to support this non-existing use case.

So I propose we lower that timeout to e.g. 5-10 minutes, or rather N times what we commonly see on Jenkins (say N=3 to be on the safe side).

Subtasks

Related issues

Has duplicate Tails - Bug #11546: Some test jobs are getting stucked in Jenkins Duplicate 2016-06-24

History

#1 Updated by intrigeri 2016-05-19 10:10:12

Thoughts? I’ve set target version = 2.6 so that we don’t feel pressured about it (no hurry, really) but it’s so trivial a change that I wouldn’t mind sneaking it into 2.4.

#2 Updated by intrigeri 2016-07-04 02:43:38

  • related to Bug #11546: Some test jobs are getting stucked in Jenkins added

#3 Updated by intrigeri 2016-07-04 02:46:32

  • related to deleted (Bug #11546: Some test jobs are getting stucked in Jenkins)

#4 Updated by intrigeri 2016-07-04 02:46:56

  • has duplicate Bug #11546: Some test jobs are getting stucked in Jenkins added

#5 Updated by intrigeri 2016-07-04 02:51:21

  • Priority changed from Normal to High

This problem recently got noticed more widely (since I wasn’t on sysadmin duty killing test jobs manually on Jenkins => Bug #11546), so bumping priority. anonym, bertagaz: thoughts? Shall I go ahead and do that in our base branches?

#6 Updated by anonym 2016-09-02 03:05:06

  • Status changed from Confirmed to In Progress
  • Assignee changed from anonym to intrigeri
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to test/11449-decrease-timeouts

I managed to find a failure video that showed the full boot, and then it took 1:32, so I propose 5 minutes.

#7 Updated by intrigeri 2016-09-02 03:24:37

  • Assignee changed from intrigeri to bertagaz

Reassigning to bertagaz, who committed to do quick reviews for anonym’s test suite stuff.

#8 Updated by intrigeri 2016-09-09 14:48:57

Ping?

#9 Updated by anonym 2016-09-20 16:54:08

  • Target version changed from Tails_2.6 to Tails_2.7

#10 Updated by intrigeri 2016-09-24 02:08:05

  • Feature Branch changed from test/11449-decrease-timeouts to test/11449-decrease-boot-timeout

#11 Updated by intrigeri 2016-09-24 02:09:25

Merged current stable into the branch to avoid issues caused by Feature #11818.

#12 Updated by bertagaz 2016-10-04 13:10:00

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Applied in changeset commit:3f6e7d6733a8ac3b8a853bfdf74525fc460b7651.

#13 Updated by bertagaz 2016-10-04 13:22:59

  • Assignee deleted (bertagaz)
  • QA Check changed from Ready for QA to Pass

Makes sense and does not seem to be problematic either at home or in Jenkins, so merged it, congrats!

#14 Updated by intrigeri 2016-10-24 10:48:54

  • Type of work changed from Discuss to Code
  • Deliverable for set to 270

#15 Updated by bertagaz 2016-11-15 18:23:33

  • Status changed from Fix committed to Resolved