Project Number Date
test_Tails_ISO_21461-update-chutney 19 10 Aug 2026, 22:19

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:39.402 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:14.910
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.144
When I start Tails from USB drive "old" with network unplugged 57.698
Then the boot device has safe access rights 2.369
And Tails is running from USB drive "old" 0.199
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.155
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.684
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.731
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 46.158
Then Tails is running from USB drive "old" 0.211
And I create a persistent partition 23.325
And I take note of which tps features are available 6.873
Then a Tails persistence partition exists on USB drive "old" 0.481
And I shutdown Tails and wait for the computer to power off 2.602
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.004
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.076
Then Tails is running from USB drive "old" 0.219
And all tps features are active 7.352
When I write some files expected to persist 1.228
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.609
And I take note of which tps features are available 6.101
And I shutdown Tails and wait for the computer to power off 2.522
# 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.405
After features/support/hooks.rb:339 0.269
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.400
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 without a persistent partition and stopped at Tails Greeter's login screen 8.013
And I log in to a new session 11.000
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.613
And I plug USB drive "to_upgrade" 2.323
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.603
Then the running Tails is installed on USB drive "to_upgrade" 18.577
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 1.628
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.223
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.569
Then all tps features from the old Tails version are active 1.221
And Tails is running from USB drive "to_upgrade" 0.193
And the boot device has safe access rights 2.486
And the expected persistent files created with the old Tails version are present in the filesystem 1.038
And all persistent directories from the old Tails version have safe access rights 1.638
After features/support/hooks.rb:339 0.941
After features/support/hooks.rb:108 0.029
3:53.657
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 21.823
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.375
When the network is plugged 0.029
And Tor is ready 12.888
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.927
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.048
Given I shutdown Tails and wait for the computer to power off 5.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.769
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 10.418
And the file system changes introduced in version 6.2~testoverlayfs are present 0.190
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.129
# 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.191
When the network is plugged 0.037
And Tor is ready 10.288
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.153
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.303
Given I shutdown Tails and wait for the computer to power off 2.637
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.508
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.169
And the file system changes introduced in version 6.3~testoverlayfs are present 0.271
And only the 6.3~testoverlayfs SquashFS delta is installed 0.029
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.172
When the network is plugged 0.025
And Tor is ready 10.311
Then the Upgrader considers the system as up-to-date 10.407
# 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.111
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:339 0.750
After features/support/hooks.rb:108 0.016
18.473
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.744
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.336
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.044
After features/support/hooks.rb:339 0.761
After features/support/hooks.rb:108 0.000