Project Number Date
test_Tails_ISO_devel 3679 04 Feb 2025, 00:11

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 21:39.244 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
3:8.739
Before features/support/hooks.rb:269 0.003
Given a computer 0.338
And I create a 7200 MiB disk named "old" 0.092
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 1:16.623
When I start Tails from USB drive "old" with network unplugged 1:45.442
Then the boot device has safe access rights 3.853
And Tails is running from USB drive "old" 0.460
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.423
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:326 4.000
After features/support/hooks.rb:100 0.006
Tags: @product
2:18.481
Before features/support/hooks.rb:269 0.003
Given a computer 0.263
And I start Tails from USB drive "old" with network unplugged and I login 1:32.890
Then Tails is running from USB drive "old" 0.481
And I create a persistent partition 33.393
And I take note of which tps features are available 1.649
Then a Tails persistence partition exists on USB drive "old" 1.021
And I shutdown Tails and wait for the computer to power off 8.781
After features/support/hooks.rb:326 0.232
After features/support/hooks.rb:100 0.006
Tags: @product
2:56.170
Before features/support/hooks.rb:269 0.002
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.148
Then Tails is running from USB drive "old" 1.012
And all tps features are active 2.379
When I write some files expected to persist 1.932
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.870
And I take note of which tps features are available 0.636
And I shutdown Tails and wait for the computer to power off 4.356
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.914
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.642
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 33.525
And I log in to a new session 21.410
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.683
And I plug USB drive "to_upgrade" 2.627
When I upgrade Tails to USB drive "to_upgrade" by cloning 30.395
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:1038:in `launch_app'
./features/step_definitions/common_steps.rb:1053:in `launch_gnome_terminal'
./features/step_definitions/common_steps.rb:931: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:326 10.840 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 02:13:19)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3679/artifact/build-artifacts/02:13:19_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3679/artifact/build-artifacts/02:13:19_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3679/artifact/build-artifacts/02:13:19_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.406
Before features/support/hooks.rb:269 0.003
Given a computer 0.242
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.745
Then all tps features from the old Tails version are active 1.943
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.653
And the expected persistent files created with the old Tails version are present in the filesystem 1.699
And all persistent directories from the old Tails version have safe access rights 2.790
After features/support/hooks.rb:326 0.678
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
8:33.378
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.537
And no SquashFS delta is installed 0.205
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
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.534
When the network is plugged 0.094
And Tor is ready 20.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.333
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.671
Given I shutdown Tails and wait for the computer to power off 1:30.803
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.145
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.818
And the file system changes introduced in version 6.2~testoverlayfs are present 0.410
And only the 6.2~testoverlayfs SquashFS delta is installed 0.111
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.376
# 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.392
When the network is plugged 0.107
And Tor is ready 19.714
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.017
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.978
Given I shutdown Tails and wait for the computer to power off 4.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.397
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.671
And the file system changes introduced in version 6.3~testoverlayfs are present 0.654
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.455
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.101
And Tor is ready 21.980
Then the Upgrader considers the system as up-to-date 0.334
# 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 17.954
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.248
After features/support/hooks.rb:326 0.962
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
43.425
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.754
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.592
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.133
And Tor is ready 20.262
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.537
After features/support/hooks.rb:326 0.834
After features/support/hooks.rb:100 0.000