Bug #16819

Failing scenario: Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Added by hefee 2019-06-18 12:30:25 . Updated 2019-06-19 08:22:25 .

Status:
Resolved
Priority:
Elevated
Assignee:
intrigeri
Category:
Test suite
Target version:
Tails_4.0
Start date:
Due date:
% Done:

100%

Feature Branch:
test/16819-buggy-asp-step
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Additional Software Packages
Deliverable for:

Description

The Scenario “Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online” is failing everytime.

The video shows at 101:10 “Additional software installed successfully” notification instead of “The upgrade of your additional software failed” notification. This indicates that the code is broken, that should be tested.

Files

02_08_16_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv (2380054 B) hefee, 2019-06-18 12:27:50
debug.log (66308 B) hefee, 2019-06-18 12:29:51

Subtasks

History

#1 Updated by intrigeri 2019-06-18 13:15:03

  • Assignee set to intrigeri

It’s a really corner-corner case, so what I see as a blocker for 4.0~beta1 is “make sure current buggy behavior is not dangerous”. I’ll do that. Then we can fix the bug in beta2 or something.

#2 Updated by intrigeri 2019-06-18 13:49:10

  • Affected tool set to Additional Software Packages

#3 Updated by intrigeri 2019-06-18 14:47:11

  • Category set to Test suite
  • Status changed from Confirmed to In Progress

This scenario manages to upgrade cowsay to 3.03+dfsg2-6 despite “I prepare the Additional Software upgrade process to fail”. That’s because that step is buggy: ls -tr1 /var/cache/apt/archives/cowsay*.deb | head -n 1 prints /var/cache/apt/archives/cowsay_3.03+dfsg2-1_all.deb, i.e. the oldest (in terms of mtime) cowsay binary package in the APT cache, instead of “the newest cowsay package from the APT cache”, which would be cowsay_3.03+dfsg2-6_all.deb.

At this point of the scenario, said APT cache has:

-rw-r--r-- 1 root root 20296 Apr  1  2018 cowsay_3.03+dfsg2-1_all.deb
-rw-r--r-- 1 root root 20856 Feb  5 01:06 cowsay_3.03+dfsg2-6_all.deb

This code happens to work on Stretch because the mtime of cowsay_3.03+dfsg2-1_all.deb in our custom APT repo is newer than the one of Stretch’s 3.03+dfsg2-3.

#4 Updated by intrigeri 2019-06-18 14:57:26

  • Parent task set to Bug #16281
  • Feature Branch set to test/16819-buggy-asp-step

#5 Updated by intrigeri 2019-06-18 16:44:18

  • Status changed from In Progress to Needs Validation
  • Assignee deleted (intrigeri)

This scenario passes for me locally on this branch.

#6 Updated by hefee 2019-06-19 08:04:50

  • Assignee set to hefee

#7 Updated by hefee 2019-06-19 08:11:04

  • Status changed from Needs Validation to In Progress
  • Assignee changed from hefee to intrigeri

Seems fine.

#8 Updated by intrigeri 2019-06-19 08:22:26

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:tails|a22222ccb0479ae974dc6f8f0d00408998ade3cc.