Project Number Date
test_Tails_ISO_save-thunderbird-pcap 1 08 Sep 2026, 19:34

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 84 1 2 0 0 87 6 1 7 14:16.136 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:22.589
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.011
When I start Tails from USB drive "old" with network unplugged 1:3.991
Then the boot device has safe access rights 2.811
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 1.173
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.145
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 50.648
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 25.921
And I take note of which tps features are available 7.513
Then a Tails persistence partition exists on USB drive "old" 0.494
And I shutdown Tails and wait for the computer to power off 4.229
After features/support/hooks.rb:339 0.254
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.545
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.805
Then Tails is running from USB drive "old" 0.219
And all tps features are active 7.186
When I write some files expected to persist 1.110
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.306
And all persistent directories from the old Tails version have safe access rights 1.690
And I take note of which tps features are available 6.202
And I shutdown Tails and wait for the computer to power off 4.170
# 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" 11.557
After features/support/hooks.rb:339 0.287
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.843
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 8.941
And I log in to a new session 11.913
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.046
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.427
Then the running Tails is installed on USB drive "to_upgrade" 20.006
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.854
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.042
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.717
Then all tps features from the old Tails version are active 1.345
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.555
And the expected persistent files created with the old Tails version are present in the filesystem 1.117
And all persistent directories from the old Tails version have safe access rights 1.950
After features/support/hooks.rb:339 0.643
After features/support/hooks.rb:108 0.067
Tags: @product @automatic_upgrade
5:44.555
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.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.551
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.056
And Tor is ready 13.840
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.567
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.611
Given I shutdown Tails and wait for the computer to power off 5.881
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.720
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.884
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
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.101
# 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.194
When the network is plugged 0.033
And Tor is ready 10.449
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.892
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.921
Given I shutdown Tails and wait for the computer to power off 4.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.316
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.114
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.023
And Tor is ready 10.971
Then the Upgrader considers the system as up-to-date 2:0.000
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/usb.rb:1421:in `/^the Upgrader considers the system as up-to-date$/'
features/usb_upgrade.feature:120:in `Then the Upgrader considers the system as up-to-date'
# 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.996 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:19:07)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_save-thunderbird-pcap/1/artifact/build-artifacts/01:19:07_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_save-thunderbird-pcap/1/artifact/build-artifacts/01:19:07_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_save-thunderbird-pcap/1/artifact/build-artifacts/01:19:07_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_save-thunderbird-pcap/1/artifact/build-artifacts/01:19:07_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.046
Tags: @product @automatic_upgrade
33.414
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.228
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 10.258
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.543
After features/support/hooks.rb:339 0.721
After features/support/hooks.rb:108 0.000