Project Number Date
test_Tails_ISO_21461-update-chutney 9 30 Jul 2026, 22:44

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 11:18.946 Passed
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:1.665
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.106
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.113
When I start Tails from USB drive "old" with network unplugged 43.184
Then the boot device has safe access rights 2.430
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:339 3.418
After features/support/hooks.rb:108 0.006
Tags: @product
1:23.120
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login 48.419
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 24.554
And I take note of which tps features are available 6.614
Then a Tails persistence partition exists on USB drive "old" 0.525
And I shutdown Tails and wait for the computer to power off 2.578
After features/support/hooks.rb:339 0.302
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.198
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.885
Then Tails is running from USB drive "old" 0.284
And all tps features are active 8.011
When I write some files expected to persist 1.198
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.317
And all persistent directories from the old Tails version have safe access rights 1.797
And I take note of which tps features are available 6.070
And I shutdown Tails and wait for the computer to power off 2.824
# 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.533
After features/support/hooks.rb:339 0.140
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.193
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.320
And I log in to a new session 12.750
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.654
And I plug USB drive "to_upgrade" 2.334
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.738
Then the running Tails is installed on USB drive "to_upgrade" 18.141
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.895
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.019
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.100
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.682
Then all tps features from the old Tails version are active 1.039
And Tails is running from USB drive "to_upgrade" 0.187
And the boot device has safe access rights 2.211
And the expected persistent files created with the old Tails version are present in the filesystem 0.940
And all persistent directories from the old Tails version have safe access rights 1.858
After features/support/hooks.rb:339 0.684
After features/support/hooks.rb:108 0.011
3:35.880
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.593
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.332
When the network is plugged 0.021
And Tor is ready 13.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.878
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.866
Given I shutdown Tails and wait for the computer to power off 5.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.678
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.499
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.172
When the network is plugged 0.027
And Tor is ready 10.248
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.335
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.944
Given I shutdown Tails and wait for the computer to power off 4.201
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.207
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 8.090
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.032
And Tor is ready 10.471
Then the Upgrader considers the system as up-to-date 0.095
# 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 3.492
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.340
After features/support/hooks.rb:339 0.903
After features/support/hooks.rb:108 0.009
18.868
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 8.017
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.026
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.046
And Tor is ready 8.624
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.916
After features/support/hooks.rb:339 0.813
After features/support/hooks.rb:108 0.000