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

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:44.605 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.784
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.013
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 32.362
When I start Tails from USB drive "old" with network unplugged 1:39.599
Then the boot device has safe access rights 3.392
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:334 4.024
After features/support/hooks.rb:104 0.025
Tags: @product
2:16.239
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.687
And I start Tails from USB drive "old" with network unplugged and I login 1:30.532
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 32.636
And I take note of which tps features are available 2.028
Then a Tails persistence partition exists on USB drive "old" 0.899
And I shutdown Tails and wait for the computer to power off 9.097
After features/support/hooks.rb:334 0.207
After features/support/hooks.rb:104 0.010
Tags: @product
3:7.527
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.003
Then Tails is running from USB drive "old" 0.437
And all tps features are active 2.419
When I write some files expected to persist 1.924
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.642
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 6.621
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.129
After features/support/hooks.rb:334 0.154
After features/support/hooks.rb:104 0.010
Tags: @product
2:32.913
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.071
And I log in to a new session 19.456
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 2.466
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.605
Then the running Tails is installed on USB drive "to_upgrade" 22.170
And I unplug USB drive "to_upgrade" 0.238
And I unplug USB drive "__internal" 0.285
After features/support/hooks.rb:334 1.075
After features/support/hooks.rb:104 0.000
Tags: @product
2:18.428
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.645
Then all tps features from the old Tails version are active 1.961
And Tails is running from USB drive "to_upgrade" 0.444
And the boot device has safe access rights 3.827
And the expected persistent files created with the old Tails version are present in the filesystem 1.493
And all persistent directories from the old Tails version have safe access rights 2.831
After features/support/hooks.rb:334 1.399
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
7:28.904
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.625
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.880
When the network is plugged 0.188
And Tor is ready 23.056
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.091
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.879
Given I shutdown Tails and wait for the computer to power off 8.902
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.139
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.646
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.336
# 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.316
When the network is plugged 0.112
And Tor is ready 17.896
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.673
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.378
Given I shutdown Tails and wait for the computer to power off 4.487
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.498
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.700
And the file system changes introduced in version 6.3~testoverlayfs are present 0.540
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.326
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.109
And Tor is ready 20.188
Then the Upgrader considers the system as up-to-date 0.358
# 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 17.057
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.861
After features/support/hooks.rb:334 0.838
After features/support/hooks.rb:104 0.022
Tags: @product @automatic_upgrade
42.807
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 19.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.216
After features/support/hooks.rb:334 1.483
After features/support/hooks.rb:104 0.000