Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 16 06 Apr 2025, 18:46

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:48.305 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:12.184
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.245
And I create a 7200 MiB disk named "old" 0.080
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 32.295
When I start Tails from USB drive "old" with network unplugged 1:33.764
Then the boot device has safe access rights 3.612
And Tails is running from USB drive "old" 0.419
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 7.249
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.787
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:32.257
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 31.879
And I take note of which tps features are available 2.260
Then a Tails persistence partition exists on USB drive "old" 0.977
And I shutdown Tails and wait for the computer to power off 8.842
After features/support/hooks.rb:330 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.856
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.407
Then Tails is running from USB drive "old" 0.376
And all tps features are active 1.923
When I write some files expected to persist 1.706
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.638
And all persistent directories from the old Tails version have safe access rights 2.707
And I take note of which tps features are available 0.500
And I shutdown Tails and wait for the computer to power off 6.342
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.754
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.536
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.259
And I log in to a new session 20.929
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.928
And I plug USB drive "to_upgrade" 2.520
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.890
Then the running Tails is installed on USB drive "to_upgrade" 27.120
And I unplug USB drive "to_upgrade" 0.442
And I unplug USB drive "__internal" 0.444
After features/support/hooks.rb:330 2.625
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.483
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.341
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.370
Then all tps features from the old Tails version are active 1.758
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.539
And the expected persistent files created with the old Tails version are present in the filesystem 1.501
And all persistent directories from the old Tails version have safe access rights 2.627
After features/support/hooks.rb:330 1.473
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:5.021
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 11.631
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.362
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.068
And Tor is ready 21.737
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.459
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.417
Given I shutdown Tails and wait for the computer to power off 13.268
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.768
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.589
And the file system changes introduced in version 6.2~testoverlayfs are present 0.371
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.361
# 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.352
When the network is plugged 0.073
And Tor is ready 19.967
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.791
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.107
Given I shutdown Tails and wait for the computer to power off 6.445
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.383
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.183
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.509
When the network is plugged 0.072
And Tor is ready 18.741
Then the Upgrader considers the system as up-to-date 0.347
# 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 16.254
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.715
After features/support/hooks.rb:330 0.773
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
1:3.436
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 12.146
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.573
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the signing key used by the Upgrader is outdated 0.150
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 49.760
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.597
After features/support/hooks.rb:330 0.713
After features/support/hooks.rb:100 0.000