Project Number Date
test_Tails_ISO_stable 4729 20 Mar 2024, 12:10

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 16:37.533 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:46.648
Before features/support/hooks.rb:245 0.010
Given a computer 0.329
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 20.597
When I start Tails from USB drive "old" with network unplugged 1:20.654
Then the boot device has safe access rights 2.985
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:291 3.779
After features/support/hooks.rb:75 0.012
Tags: @product
2:5.989
Before features/support/hooks.rb:245 0.006
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:21.740
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 33.411
And I take note of which tps features are available 2.320
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 7.133
After features/support/hooks.rb:291 0.185
After features/support/hooks.rb:75 0.011
Tags: @product
2:36.320
Before features/support/hooks.rb:245 0.006
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.984
Then Tails is running from USB drive "old" 0.273
And all tps features are active 1.959
When I write some files expected to persist 1.564
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.762
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 4.096
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.329
After features/support/hooks.rb:291 0.126
After features/support/hooks.rb:75 0.009
Tags: @product
1:4.527
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:245 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.127
And I log in to a new session 19.108
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.413
And I plug USB drive "to_upgrade" 2.612
When I upgrade Tails to USB drive "to_upgrade" by cloning 30.265
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1015:in `launch_app'
./features/step_definitions/common_steps.rb:1029:in `launch_gnome_terminal'
./features/step_definitions/common_steps.rb:925:in `/^I run "([^"]+)" in GNOME Terminal$/'
./features/step_definitions/usb.rb:147: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 9.824 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:37:49)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4729/artifact/build-artifacts/01:37:49_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4729/artifact/build-artifacts/01:37:49_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
After features/support/hooks.rb:75 0.000
Tags: @product
2:7.017
Before features/support/hooks.rb:245 0.008
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.259
Then all tps features from the old Tails version are active 1.522
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.810
And the expected persistent files created with the old Tails version are present in the filesystem 1.412
And all persistent directories from the old Tails version have safe access rights 2.499
After features/support/hooks.rb:291 0.838
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
6:22.105
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.387
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.063
And Tor is ready 19.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.025
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.760
Given I shutdown Tails and wait for the computer to power off 8.043
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.553
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.230
And the file system changes introduced in version 6.2~testoverlayfs are present 0.391
And only the 6.2~testoverlayfs 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.314
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.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 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.034
And Tor is ready 20.288
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.839
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.836
Given I shutdown Tails and wait for the computer to power off 4.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.482
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.878
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.282
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.037
And Tor is ready 17.810
Then the Upgrader considers the system as up-to-date 10.716
# 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 13.915
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.838
After features/support/hooks.rb:291 0.775
After features/support/hooks.rb:75 0.026
Tags: @product @automatic_upgrade
34.924
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.419
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.457
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 17.040
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.606
After features/support/hooks.rb:291 0.859
After features/support/hooks.rb:75 0.000