Project Number Date
test_Tails_ISO_21582-gnome-software-traffic-is-not-sus 1 08 Sep 2026, 20:23

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 1 11 0 0 87 6 1 7 11:17.079 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:25.682
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.034
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 13.712
When I start Tails from USB drive "old" with network unplugged 1:7.533
Then the boot device has safe access rights 2.484
And Tails is running from USB drive "old" 0.266
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.262
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.616
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.679
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 51.123
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 24.170
And I take note of which tps features are available 7.200
Then a Tails persistence partition exists on USB drive "old" 0.576
And I shutdown Tails and wait for the computer to power off 4.264
After features/support/hooks.rb:339 0.228
After features/support/hooks.rb:108 0.005
Tags: @product
1:39.662
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.268
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.717
Then Tails is running from USB drive "old" 0.185
And all tps features are active 7.254
When I write some files expected to persist 1.169
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.276
And all persistent directories from the old Tails version have safe access rights 1.694
And I take note of which tps features are available 6.708
And I shutdown Tails and wait for the computer to power off 4.098
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.103
After features/support/hooks.rb:339 0.166
After features/support/hooks.rb:108 0.005
Tags: @product
2:29.761
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 23.085
And I log in to a new session 13.498
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.659
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.724
Then the running Tails is installed on USB drive "to_upgrade" 18.349
And I unplug USB drive "to_upgrade" 0.104
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.849
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.916
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.100
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.799
Then all tps features from the old Tails version are active 1.291
And Tails is running from USB drive "to_upgrade" 0.198
And the boot device has safe access rights 2.605
And the expected persistent files created with the old Tails version are present in the filesystem 1.068
And all persistent directories from the old Tails version have safe access rights 1.851
After features/support/hooks.rb:339 0.792
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
2:45.149
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.464
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.028
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.323
When the network is plugged 0.046
And Tor is ready 13.222
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.293
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.293
Given I shutdown Tails and wait for the computer to power off 6.759
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.304
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.880
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.096
# 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.237
When the network is plugged 0.069
And Tor is ready 9.875
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.710
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.725
Given I shutdown Tails and wait for the computer to power off 2.552
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 39.442
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:238:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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:339 4.843 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:15:25)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21582-gnome-software-traffic-is-not-sus/1/artifact/build-artifacts/01:15:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21582-gnome-software-traffic-is-not-sus/1/artifact/build-artifacts/01:15:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21582-gnome-software-traffic-is-not-sus/1/artifact/build-artifacts/01:15:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21582-gnome-software-traffic-is-not-sus/1/artifact/build-artifacts/01:15:25_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.228
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.983
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 8.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.739
After features/support/hooks.rb:339 1.195
After features/support/hooks.rb:108 0.000