Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 9 30 Mar 2025, 18:27

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 18:33.490 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
1:58.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.131
When I start Tails from USB drive "old" with network unplugged 1:22.571
Then the boot device has safe access rights 2.935
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.738
After features/support/hooks.rb:100 0.007
Tags: @product
2:3.172
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:20.586
Then Tails is running from USB drive "old" 0.289
And I create a persistent partition 31.807
And I take note of which tps features are available 1.368
Then a Tails persistence partition exists on USB drive "old" 0.747
And I shutdown Tails and wait for the computer to power off 8.179
After features/support/hooks.rb:330 0.166
After features/support/hooks.rb:100 0.007
Tags: @product
2:43.454
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.368
Then Tails is running from USB drive "old" 0.319
And all tps features are active 1.947
When I write some files expected to persist 1.666
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.610
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.331
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.948
After features/support/hooks.rb:330 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.088
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 without a persistent partition and stopped at Tails Greeter's login screen 9.757
And I log in to a new session 18.064
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.551
And I plug USB drive "to_upgrade" 2.439
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.589
Then the running Tails is installed on USB drive "to_upgrade" 23.201
And I unplug USB drive "to_upgrade" 0.256
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:330 0.990
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.624
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.484
Then all tps features from the old Tails version are active 1.582
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.226
And the expected persistent files created with the old Tails version are present in the filesystem 1.409
And all persistent directories from the old Tails version have safe access rights 2.395
After features/support/hooks.rb:330 1.500
After features/support/hooks.rb:100 0.009
6:23.896
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 10.689
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
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.479
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.073
And Tor is ready 21.010
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.782
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.424
Given I shutdown Tails and wait for the computer to power off 8.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.446
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.104
And the file system changes introduced in version 6.2~testoverlayfs are present 0.281
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.275
# 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.278
When the network is plugged 0.079
And Tor is ready 20.104
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.268
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.535
Given I shutdown Tails and wait for the computer to power off 4.258
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.029
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.966
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.355
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.068
And Tor is ready 19.087
Then the Upgrader considers the system as up-to-date 0.298
# 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 14.891
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.695
After features/support/hooks.rb:330 0.916
After features/support/hooks.rb:100 0.018
37.322
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.032
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.527
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.128
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 17.850
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.636
After features/support/hooks.rb:330 0.659
After features/support/hooks.rb:100 0.000