Bug #16134

devel branch FTBFS since torbrowser-launcher 0.3.1-2 was uploaded to sid

Added by intrigeri 2018-11-17 19:03:19 . Updated 2019-01-30 11:49:56 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Target version:
Tails_3.12
Start date:
2018-11-17
Due date:
% Done:

100%

Feature Branch:
bugfix/16134-torbrowser-0.3.1-2+force-all-tests
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Browser
Deliverable for:

Description

Subtasks

Related issues

Blocks Tails - Feature #15506: Core work 2018Q4: Foundations Team Resolved 2018-04-08
Blocks Tails - Bug #15776: Remove Liferea Resolved 2018-08-09
Blocks Tails - Bug #15915: Drop background readahead on boot Resolved 2018-09-05
Blocks Tails - Bug #15428: Rename our HTP pools Resolved 2018-03-19
Blocks Tails - Feature #15293: Creating & preparing the disk image Resolved 2018-02-17

History

#1 Updated by intrigeri 2018-11-17 19:03:38

#2 Updated by intrigeri 2018-11-17 19:30:59

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • Feature Branch set to bugfix/16134-torbrowser-0.3.1-2

#3 Updated by intrigeri 2018-11-17 20:06:26

#4 Updated by intrigeri 2018-11-17 20:06:37

  • blocks Bug #15915: Drop background readahead on boot added

#5 Updated by intrigeri 2018-11-17 20:06:46

#6 Updated by intrigeri 2018-11-17 20:13:57

  • Feature Branch changed from bugfix/16134-torbrowser-0.3.1-2 to bugfix/16134-torbrowser-0.3.1-2+force-all-tests

Builds fine.

#7 Updated by intrigeri 2018-11-17 20:14:06

  • Affected tool set to Browser

#8 Updated by intrigeri 2018-11-17 20:15:10

segfault, no need to duplicate this work :)

I’m waiting to check the test suite results on Jenkins before sending your way for review, but feel free to pick it before and check Jenkins yourself.

#9 Updated by intrigeri 2018-11-18 07:45:43

#10 Updated by intrigeri 2018-11-19 07:44:17

  • Assignee changed from intrigeri to segfault
  • % Done changed from 10 to 50
  • QA Check set to Ready for QA

In 2 full test suite runs, putting aside unrelated failures: only one browser scenario failed, in one of the two runs; that’s a well-known fragile test and I doubt this branch could possibly make it fail only occasionally (I would expect this branch to break things every time, if at all). Please review & merge into devel :)

#11 Updated by segfault 2018-11-20 10:09:56

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

Applied in changeset commit:tails|a0a0fed04de582f53eb56022301a0ed63e2d015c.

#12 Updated by segfault 2018-11-20 10:13:17

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

#13 Updated by anonym 2019-01-30 11:49:56

  • Status changed from Fix committed to Resolved