Project Number Date
test_Tails_ISO_stable 4671 17 Feb 2024, 11:59

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 83 1 3 0 0 87 6 1 7 15:46.865 Failed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
1:24.470
Before features/support/hooks.rb:245 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 19.253
When I start Tails from USB drive "old" with network unplugged 59.312
Then the boot device has safe access rights 3.559
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:291 3.772
After features/support/hooks.rb:75 0.019
Tags: @product
2:2.556
Before features/support/hooks.rb:245 0.020
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:9.077
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 42.344
And I take note of which tps features are available 1.501
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 8.253
After features/support/hooks.rb:291 0.154
After features/support/hooks.rb:75 0.009
Tags: @product
2:23.168
Before features/support/hooks.rb:245 0.004
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.362
Then Tails is running from USB drive "old" 0.439
And all tps features are active 2.418
When I write some files expected to persist 2.178
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.327
And all persistence configuration files have safe access rights 0.586
And all persistent directories from the old Tails version have safe access rights 3.596
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 4.173
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.389
After features/support/hooks.rb:291 0.098
After features/support/hooks.rb:75 0.011
Tags: @product
1:0.820
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:245 0.006
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.087
And I log in to a new session 18.813
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.059
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 28.356
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "tails-installer" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:148:in `new'
./features/step_definitions/usb.rb:148:in `/^I start Tails Installer$/'
./features/step_definitions/usb.rb:187:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_upgrade.feature:65:in `When I upgrade Tails to USB drive "to_upgrade" by cloning'
Then the running Tails is installed on USB drive "to_upgrade" 0.000
And I unplug USB drive "to_upgrade" 0.000
And I unplug USB drive "__internal" 0.000
After features/support/hooks.rb:291 4.458 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:23:34)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4671/artifact/build-artifacts/01:23:34_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4671/artifact/build-artifacts/01:23:34_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4671/artifact/build-artifacts/01:23:34_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4671/artifact/build-artifacts/01:23:34_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:75 0.000
Tags: @product
2:11.165
Before features/support/hooks.rb:245 0.005
Given a computer 0.687
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.363
Then all tps features from the old Tails version are active 3.541
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 4.514
And the expected persistent files created with the old Tails version are present in the filesystem 1.580
And all persistent directories from the old Tails version have safe access rights 3.167
After features/support/hooks.rb:291 0.919
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:16.327
Before features/support/hooks.rb:245 0.023
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.335
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.416
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.066
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.428
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.660
When the network is plugged 0.035
And Tor is ready 19.671
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.941
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.978
Given I shutdown Tails and wait for the computer to power off 11.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.588
Then Tails is running version 2.2~testoverlayfsng 0.115
And all tps features are active 2.272
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.434
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.320
When the network is plugged 0.034
And Tor is ready 14.488
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.913
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.688
Given I shutdown Tails and wait for the computer to power off 3.382
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.243
Then Tails is running version 2.3~testoverlayfsng 0.141
And all tps features are active 2.527
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.570
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.075
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.373
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.344
When the network is plugged 0.052
And Tor is ready 13.647
Then the Upgrader considers the system as up-to-date 10.893
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 27.832
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.083
After features/support/hooks.rb:291 0.848
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
28.356
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.081
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.410
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.107
And the signing key used by the Upgrader is outdated 0.684
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 15.302
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.734
After features/support/hooks.rb:291 1.345
After features/support/hooks.rb:75 0.000