Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 33 24 Apr 2025, 12:57

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 19:38.964 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:4.172
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.839
When I start Tails from USB drive "old" with network unplugged 1:28.643
Then the boot device has safe access rights 3.390
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 8.427
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.855
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:26.452
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 31.039
And I take note of which tps features are available 1.607
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.428
After features/support/hooks.rb:330 0.213
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.600
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.279
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.686
Then Tails is running from USB drive "old" 0.320
And all tps features are active 2.117
When I write some files expected to persist 1.891
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.476
And I take note of which tps features are available 0.397
And I shutdown Tails and wait for the computer to power off 4.254
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.554
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.686
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 without a persistent partition and stopped at Tails Greeter's login screen 11.845
And I log in to a new session 20.382
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.675
And I plug USB drive "to_upgrade" 2.497
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.212
Then the running Tails is installed on USB drive "to_upgrade" 25.621
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:330 0.862
After features/support/hooks.rb:100 0.000
Tags: @product
2:36.180
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.649
Then all tps features from the old Tails version are active 1.896
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.916
And the expected persistent files created with the old Tails version are present in the filesystem 1.510
And all persistent directories from the old Tails version have safe access rights 2.671
After features/support/hooks.rb:330 1.518
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:43.086
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.713
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.415
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.591
When the network is plugged 0.106
And Tor is ready 18.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.464
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.092
Given I shutdown Tails and wait for the computer to power off 8.818
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.093
Then Tails is running version 6.2~testoverlayfs 0.036
And all tps features are active 2.192
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.267
When the network is plugged 0.071
And Tor is ready 19.792
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.886
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.559
Given I shutdown Tails and wait for the computer to power off 4.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.939
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.512
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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.303
When the network is plugged 0.065
And Tor is ready 20.008
Then the Upgrader considers the system as up-to-date 0.345
# 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.414
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.487
After features/support/hooks.rb:330 0.784
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
33.382
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 16.121
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.465
After features/support/hooks.rb:330 0.778
After features/support/hooks.rb:100 0.000