Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 22 13 Apr 2025, 18:25

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 20:8.301 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
2:17.619
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.506
And I create a 7200 MiB disk named "old" 0.193
And I plug USB drive "old" 1.205
And I write an old version of the Tails USB image to disk "old" 31.711
When I start Tails from USB drive "old" with network unplugged 1:39.760
Then the boot device has safe access rights 3.195
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:330 7.189
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.477
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.273
And I start Tails from USB drive "old" with network unplugged and I login 1:26.960
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 31.290
And I take note of which tps features are available 2.289
Then a Tails persistence partition exists on USB drive "old" 0.824
And I shutdown Tails and wait for the computer to power off 8.467
After features/support/hooks.rb:330 0.198
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.733
Then Tails is running from USB drive "old" 0.497
And all tps features are active 2.132
When I write some files expected to persist 1.976
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.317
And all persistence configuration files have safe access rights 0.695
And all persistent directories from the old Tails version have safe access rights 2.976
And I take note of which tps features are available 0.497
And I shutdown Tails and wait for the computer to power off 6.850
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.500
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.281
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 without a persistent partition and stopped at Tails Greeter's login screen 11.609
And I log in to a new session 20.171
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.607
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.565
Then the running Tails is installed on USB drive "to_upgrade" 21.354
And I unplug USB drive "to_upgrade" 0.252
And I unplug USB drive "__internal" 0.259
After features/support/hooks.rb:330 3.852
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.381
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.008
Then all tps features from the old Tails version are active 1.925
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.631
And the expected persistent files created with the old Tails version are present in the filesystem 1.513
And all persistent directories from the old Tails version have safe access rights 2.739
After features/support/hooks.rb:330 1.552
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:3.014
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.045
And no SquashFS delta is installed 0.218
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.544
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.384
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.090
And Tor is ready 22.208
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.176
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.210
Given I shutdown Tails and wait for the computer to power off 8.637
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.842
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.271
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.315
When the network is plugged 0.089
And Tor is ready 18.649
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.039
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.469
Given I shutdown Tails and wait for the computer to power off 6.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.596
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.209
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.332
When the network is plugged 0.075
And Tor is ready 17.901
Then the Upgrader considers the system as up-to-date 0.317
# 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.142
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.674
After features/support/hooks.rb:330 0.724
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
38.152
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 10.699
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.513
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 20.153
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.549
After features/support/hooks.rb:330 1.176
After features/support/hooks.rb:100 0.000