Bug #15141

reproducibly_build_Tails_ISO_stable job erroneously fails when build reproduction succeeded

Added by intrigeri 2018-01-02 09:55:59 . Updated 2018-08-21 11:39:11 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Tails_3.9
Start date:
2018-01-02
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:
301

Description

Since yesterday the artifacts signing fails, which fails the build. I suspect this is caused by the upgrade of diffoscope to 90: apparently no empty diffoscope.txt is created anymore.

Subtasks

History

#1 Updated by intrigeri 2018-01-02 10:09:25

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

Deployed a tentative fix: https://git-tails.immerda.ch/puppet-tails/commit/?id=fc308cca6dd04f17319c8800363d2f5188c8be59. Let’s see how it goes.

#2 Updated by intrigeri 2018-01-02 12:12:20

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

Seems to work when the ISO could be reproduced: https://jenkins.tails.boum.org/job/reproducibly_build_Tails_ISO_stable/98/. So I’ll assume it works too when the ISO cannot be reproduced (my understanding is that the former case is more likely to trigger bugs in that script than the latter).

#3 Updated by anonym 2018-01-23 19:52:29

  • Target version changed from Tails_3.5 to Tails_3.6

#4 Updated by bertagaz 2018-03-14 10:57:51

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

#5 Updated by intrigeri 2018-03-29 14:43:44

  • Deliverable for changed from SponsorS_Internal to 301

#7 Updated by bertagaz 2018-05-10 11:09:01

  • Target version changed from Tails_3.7 to Tails_3.8

#8 Updated by intrigeri 2018-06-26 16:27:38

  • Target version changed from Tails_3.8 to Tails_3.9

#11 Updated by intrigeri 2018-08-21 11:39:11

  • Status changed from In Progress to Resolved
  • Assignee deleted (bertagaz)
  • % Done changed from 50 to 100
  • QA Check deleted (Ready for QA)

I’ve not seen this problem happen again and it feels futile to wait any longer for a review, so let’s call it done.