Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 32 23 Apr 2025, 19:21

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 22:14.249 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
3:2.802
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.285
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 1:5.630
When I start Tails from USB drive "old" with network unplugged 1:50.615
Then the boot device has safe access rights 3.822
And Tails is running from USB drive "old" 0.511
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.371
And I unplug USB drive "old" 0.247
After features/support/hooks.rb:330 8.846
After features/support/hooks.rb:100 0.013
Tags: @product
2:15.376
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:29.659
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 31.904
And I take note of which tps features are available 3.702
Then a Tails persistence partition exists on USB drive "old" 0.945
And I shutdown Tails and wait for the computer to power off 8.579
After features/support/hooks.rb:330 0.167
After features/support/hooks.rb:100 0.010
Tags: @product
3:8.186
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.279
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.925
Then Tails is running from USB drive "old" 0.402
And all tps features are active 2.456
When I write some files expected to persist 2.202
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.831
And I take note of which tps features are available 0.687
And I shutdown Tails and wait for the computer to power off 4.742
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.950
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.018
Tags: @product
3:0.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 18.077
And I log in to a new session 20.324
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.750
And I plug USB drive "to_upgrade" 2.391
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.598
Then the running Tails is installed on USB drive "to_upgrade" 33.092
And I unplug USB drive "to_upgrade" 0.261
And I unplug USB drive "__internal" 0.285
After features/support/hooks.rb:330 1.039
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.705
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.309
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.877
Then all tps features from the old Tails version are active 2.098
And Tails is running from USB drive "to_upgrade" 0.438
And the boot device has safe access rights 3.762
And the expected persistent files created with the old Tails version are present in the filesystem 1.595
And all persistent directories from the old Tails version have safe access rights 2.623
After features/support/hooks.rb:330 1.371
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:36.906
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 29.382
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.412
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.111
And Tor is ready 22.238
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.446
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.796
Given I shutdown Tails and wait for the computer to power off 10.975
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.934
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 10.663
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.369
# 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.384
When the network is plugged 0.712
And Tor is ready 20.138
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.859
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.927
Given I shutdown Tails and wait for the computer to power off 4.540
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.945
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.682
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.326
When the network is plugged 0.095
And Tor is ready 23.654
Then the Upgrader considers the system as up-to-date 0.410
# 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.490
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.931
After features/support/hooks.rb:330 0.834
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
44.491
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 15.356
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.433
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
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.126
And Tor is ready 21.462
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.916
After features/support/hooks.rb:330 2.123
After features/support/hooks.rb:100 0.000