Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 29 20 Apr 2025, 18:55

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:26.500 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:7.491
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 32.259
When I start Tails from USB drive "old" with network unplugged 1:29.850
Then the boot device has safe access rights 3.174
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:330 3.503
After features/support/hooks.rb:100 0.006
Tags: @product
2:17.219
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:32.163
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 33.223
And I take note of which tps features are available 2.347
Then a Tails persistence partition exists on USB drive "old" 0.706
And I shutdown Tails and wait for the computer to power off 8.228
After features/support/hooks.rb:330 0.183
After features/support/hooks.rb:100 0.006
Tags: @product
3:4.419
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 with persistence enabled 2:24.399
Then Tails is running from USB drive "old" 0.401
And all tps features are active 2.058
When I write some files expected to persist 2.533
# 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.437
And all persistent directories from the old Tails version have safe access rights 2.708
And I take note of which tps features are available 0.481
And I shutdown Tails and wait for the computer to power off 6.443
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.568
After features/support/hooks.rb:330 0.112
After features/support/hooks.rb:100 0.006
Tags: @product
2:28.233
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.642
And I log in to a new session 18.920
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.607
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.755
Then the running Tails is installed on USB drive "to_upgrade" 20.388
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 0.725
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.505
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.156
Then all tps features from the old Tails version are active 1.724
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.470
And the expected persistent files created with the old Tails version are present in the filesystem 1.331
And all persistent directories from the old Tails version have safe access rights 2.344
After features/support/hooks.rb:330 1.204
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:28.235
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.973
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
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.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.066
And Tor is ready 22.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.570
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.804
Given I shutdown Tails and wait for the computer to power off 8.493
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.592
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.394
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.266
When the network is plugged 0.061
And Tor is ready 19.519
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.997
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.380
Given I shutdown Tails and wait for the computer to power off 4.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.837
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.361
When the network is plugged 0.071
And Tor is ready 19.956
Then the Upgrader considers the system as up-to-date 0.313
# 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.949
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.150
After features/support/hooks.rb:330 0.687
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
41.395
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.449
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.104
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 22.598
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.778
After features/support/hooks.rb:330 0.977
After features/support/hooks.rb:100 0.000