Project

General

Profile

Bug #12491

Test suite fails to start Chutney, which breaks all online tests on Jenkins

Added by intrigeri about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Test suite
Target version:
Start date:
04/29/2017
Due date:
% Done:

100%

QA Check:
Pass
Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

Since a few days, it looks like all tests that depend on Tor boostrapping fail. I see no relevant code changes so maybe it's an infra problem? I've just restarted shorewall on lizard, in case it might help.


Related issues

Duplicated by Tails - Bug #12512: Chutney nodes affected by Tor sandbox violation Duplicate 05/05/2017
Blocks Tails - Feature #11983: Check if the test suite has more failures on the reproducible ISO Resolved 11/21/2016
Blocks Tails - Feature #12468: Rebase isotesters' custom QEMU on 1:2.8+dfsg-4 Resolved 04/22/2017

History

#1 Updated by intrigeri about 1 year ago

  • Subject changed from ISO tests fail on Jenkins: Tor fails to bootstrap to Test suite fails to start Chutney, which breaks all online tests on Jenkins
  • Category changed from Continuous Integration to Test suite
  • Assignee changed from bertagaz to anonym
  • Priority changed from Elevated to High
  • Type of work changed from Sysadmin to Code

On isotesters, I see that only the obfs4 Tor instances are running. I suspect it's the very same issue (with Sandbox 1 being the default except for obfs4) that anonym and I have seen locally, that has eventually propagated to our (Stretch) isotesters. Setting high priority as this breaks most of our automated QA.

#2 Updated by intrigeri about 1 year ago

  • Blocks Feature #11983: Check if the test suite has more failures on the reproducible ISO added

#3 Updated by intrigeri about 1 year ago

  • Blocks Feature #12468: Rebase isotesters' custom QEMU on 1:2.8+dfsg-4 added

#4 Updated by anonym about 1 year ago

  • Duplicated by Bug #12512: Chutney nodes affected by Tor sandbox violation added

#5 Updated by anonym about 1 year ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 30
  • QA Check set to Ready for QA

From my duplicate:

Fix (tested locally) pushed with 60dc1d356c7b14ec24b59569c576d1f6787a5759 to all base branches. Let's see what Jenkins thinks!

#6 Updated by intrigeri about 1 year ago

  • Status changed from In Progress to Resolved
  • Assignee deleted (anonym)
  • % Done changed from 30 to 100
  • QA Check changed from Ready for QA to Pass

It's fixed, thanks :)

Also available in: Atom PDF