Project Number Date
test_Tails_ISO_devel 3902 08 Jul 2025, 13:36

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 73 1 13 0 0 87 6 1 7 24:29.283 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
2:56.480
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 41.613
When I start Tails from USB drive "old" with network unplugged 2:0.872
Then the boot device has safe access rights 4.380
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.786
And I unplug USB drive "old" 7.005
After features/support/hooks.rb:330 3.784
After features/support/hooks.rb:100 0.012
Tags: @product
3:5.003
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 2:2.995
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 44.647
And I take note of which tps features are available 4.536
Then a Tails persistence partition exists on USB drive "old" 3.122
And I shutdown Tails and wait for the computer to power off 9.102
After features/support/hooks.rb:330 0.263
After features/support/hooks.rb:100 0.010
Tags: @product
4:15.749
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:16.566
Then Tails is running from USB drive "old" 0.384
And all tps features are active 2.164
When I write some files expected to persist 2.517
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.310
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 7.529
And I take note of which tps features are available 0.773
And I shutdown Tails and wait for the computer to power off 7.224
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.632
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.008
Tags: @product
3:37.578
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.093
And I log in to a new session 29.279
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.591
And I plug USB drive "to_upgrade" 4.324
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.281
Then the running Tails is installed on USB drive "to_upgrade" 46.011
And I unplug USB drive "to_upgrade" 3.920
And I unplug USB drive "__internal" 1.076
After features/support/hooks.rb:330 2.552
After features/support/hooks.rb:100 0.000
Tags: @product
3:25.196
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.235
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:10.022
Then all tps features from the old Tails version are active 4.824
And Tails is running from USB drive "to_upgrade" 0.788
And the boot device has safe access rights 4.182
And the expected persistent files created with the old Tails version are present in the filesystem 1.703
And all persistent directories from the old Tails version have safe access rights 3.439
After features/support/hooks.rb:330 4.189
After features/support/hooks.rb:100 0.144
Tags: @product @automatic_upgrade
6:3.572
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.031
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.923
And no SquashFS delta is installed 0.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.630
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.127
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.632
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.747
When the network is plugged 0.148
And Tor is ready 27.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.657
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.106
Given I shutdown Tails and wait for the computer to power off 17.359
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:24.605
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.849
And the file system changes introduced in version 6.2~testoverlayfs are present 0.397
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.356
When the network is plugged 0.077
And Tor is ready 33.852
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.061
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.493
cannot 
cannot find TailsUpgraderApplyUpgradeButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/usb.rb:1327:in `/^I can successfully install the incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:107:in `And I can successfully install the incremental upgrade to version 6.3~testoverlayfs'
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 5.714 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:37:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3902/artifact/build-artifacts/02:37:36_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3902/artifact/build-artifacts/02:37:36_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3902/artifact/build-artifacts/02:37:36_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3902/artifact/build-artifacts/02:37:36_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
1:5.701
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.760
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.115
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.148
And the signing key used by the Upgrader is outdated 0.126
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 39.831
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.615
After features/support/hooks.rb:330 1.328
After features/support/hooks.rb:100 0.000