Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 3 28 Mar 2025, 18:17

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 18:22.975 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:52.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.201
When I start Tails from USB drive "old" with network unplugged 1:18.628
Then the boot device has safe access rights 2.861
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 6.830
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.424
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:19.898
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 31.694
And I take note of which tps features are available 1.346
Then a Tails persistence partition exists on USB drive "old" 0.762
And I shutdown Tails and wait for the computer to power off 8.242
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.008
Tags: @product
2:43.669
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.955
Then Tails is running from USB drive "old" 0.339
And all tps features are active 1.907
When I write some files expected to persist 1.604
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.602
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 4.298
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.684
After features/support/hooks.rb:330 0.115
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.574
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.910
And I log in to a new session 18.000
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.341
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.369
Then the running Tails is installed on USB drive "to_upgrade" 20.083
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:330 1.968
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.755
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.907
Then all tps features from the old Tails version are active 1.848
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.048
And the expected persistent files created with the old Tails version are present in the filesystem 1.785
And all persistent directories from the old Tails version have safe access rights 2.670
After features/support/hooks.rb:330 1.738
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:28.035
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.283
And no SquashFS delta is installed 0.563
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.449
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.093
And Tor is ready 21.889
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.627
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.809
Given I shutdown Tails and wait for the computer to power off 8.833
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.712
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.030
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.279
# 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.264
When the network is plugged 0.079
And Tor is ready 17.524
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.626
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.269
Given I shutdown Tails and wait for the computer to power off 4.631
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.966
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.888
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.073
And Tor is ready 18.703
Then the Upgrader considers the system as up-to-date 0.300
# 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 15.558
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.273
After features/support/hooks.rb:330 0.892
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.602
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.667
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.699
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.097
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 18.609
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.354
After features/support/hooks.rb:330 0.733
After features/support/hooks.rb:100 0.000