Project

General

Profile

Bug #11590

Bug #10988: Tails Installer workarounds for UDisks 2 bugs are not robust enough

Improve Tails Installer robustness for 2.6

Added by intrigeri about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Elevated
Assignee:
-
Category:
Installation
Target version:
Start date:
07/22/2016
Due date:
% Done:

100%

Feature Branch:
bugfix/11590-installer-robustness, installer:bugfix/10720-installer-freezes-on-jenkins
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Installer

Description

This ticket is about the iteration aimed at 2.6 of the improvements I've been working on as part of #10720. The goal is to get the installer robustness & debugging improvements produced there into 2.6, so that they benefit human users even though they might not be good enough to mark the tests as non-fragile on Jenkins yet (and close #10720).


Related issues

Blocks Tails - Bug #11582: Some upgrade test scenarios fail due to lack of disk space on Jenkins Resolved 07/21/2016
Blocks Tails - Bug #11588: Sometimes fails to boot from USB on Jenkins with I/O errors Resolved 07/22/2016

Associated revisions

Revision 3c02ea74 (diff)
Added by intrigeri about 3 years ago

Revert "Revert "Mark as fragile all tests that rely on Tails Installer.""

This reverts commit 47d9d43faf498d00e3ef09fdacd1c2e1119121e0.

refs: #11590

Revision 20d07239 (diff)
Added by intrigeri about 3 years ago

Revert "Revert "Test suite: mark "Scenario: Tails shuts down on USB boot medium removal" as fragile.""

This reverts commit bfb67b1ef29e62fea439176c04e16c91ee0b3f46.

refs: #11590

Revision ed295ad8 (diff)
Added by intrigeri about 3 years ago

Drop version-based APT pinning for Tails Installer.

That pinning has been useful for #10720 so far, but we don't want to
merge it into one of our release branches. And once this branch is
merged into one of our release branches, and flows into the branch for

refs: #11590

Revision bd961bd8
Added by anonym almost 3 years ago

Merge remote-tracking branch 'origin/feature/from-intrigeri-for-2.6' into devel

Fix-committed: #5650, #6729, #6850, #8485, #10190, #10298, #10733, #10733, #11281, #11588, #11582, #11590

History

#1 Updated by intrigeri about 3 years ago

  • Blocks Bug #11582: Some upgrade test scenarios fail due to lack of disk space on Jenkins added

#2 Updated by intrigeri about 3 years ago

  • Feature Branch set to bugfix/11590-installer-robustness, installer:bugfix/10720-installer-freezes-on-jenkins

Please review and merge:

  • tails.git: bugfix/11590-installer-robustness into devel
  • Installer: bugfix/10720-installer-freezes-on-jenkins into master

Sorry, the Git history is awful (reverts and reverts of reverts all the way), so I recommend looking at the diff first, and using git blame/log/show only if that's needed to understand specific changes.

Note that this review'n'merge is also about #11590.

#3 Updated by intrigeri about 3 years ago

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

#4 Updated by intrigeri about 3 years ago

Alan: you might want to have a look at the bugfix/10720-installer-freezes-on-jenkins branch on the Installer repo, since you're the one of us who's the most at ease with udisks crazyness. FYI these changes make Tails Installer work on Jenkins, while it has been failing 100% of the time since 6 months there.

#5 Updated by intrigeri almost 3 years ago

  • Blocks Bug #11588: Sometimes fails to boot from USB on Jenkins with I/O errors added

#6 Updated by intrigeri almost 3 years ago

I'd like to ease reviewing for the 2.6 RM, and to get automated tests running about the combination of all these changes ASAP in the 2.6 dev cycle. So, I've merged this work, along with the other major branches I'm proposing for 2.6, into the feature/from-intrigeri-for-2.6 integration branch (Jenkins builds and tests).

#7 Updated by anonym almost 3 years ago

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

#8 Updated by anonym almost 3 years ago

  • Status changed from Fix committed to Resolved

Also available in: Atom PDF