Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 971
    • Issues 971
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #11449
Closed
Open
Issue created May 19, 2016 by intrigeri@intrigeriMaintainer

Decrease boot timeout in the test suite

Originally created by @intrigeri on #11449 (Redmine)

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).

Feature Branch: test/11449-decrease-boot-timeout

Related issues

  • Has duplicate #11546 (closed)
Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking