Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 21 12 Apr 2025, 18:36

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:9.665 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:51.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.287
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 1:7.367
When I start Tails from USB drive "old" with network unplugged 1:38.153
Then the boot device has safe access rights 3.773
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:330 7.077
After features/support/hooks.rb:100 0.012
Tags: @product
2:13.888
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.295
And I start Tails from USB drive "old" with network unplugged and I login 1:27.741
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 33.754
And I take note of which tps features are available 2.341
Then a Tails persistence partition exists on USB drive "old" 0.856
And I shutdown Tails and wait for the computer to power off 8.576
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.870
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.832
Then Tails is running from USB drive "old" 0.498
And all tps features are active 2.210
When I write some files expected to persist 1.953
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.598
And all persistent directories from the old Tails version have safe access rights 2.754
And I take note of which tps features are available 0.489
And I shutdown Tails and wait for the computer to power off 4.425
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.665
After features/support/hooks.rb:330 0.127
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.406
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 11.099
And I log in to a new session 19.176
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.602
And I plug USB drive "to_upgrade" 2.408
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.042
Then the running Tails is installed on USB drive "to_upgrade" 26.634
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 2.431
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.814
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.415
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.190
Then all tps features from the old Tails version are active 1.707
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.770
And the expected persistent files created with the old Tails version are present in the filesystem 1.675
And all persistent directories from the old Tails version have safe access rights 2.689
After features/support/hooks.rb:330 1.690
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:24.265
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 10.992
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.725
When the network is plugged 0.069
And Tor is ready 20.464
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.231
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.768
Given I shutdown Tails and wait for the computer to power off 8.717
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.364
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.276
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.309
When the network is plugged 0.081
And Tor is ready 19.427
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.355
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.826
Given I shutdown Tails and wait for the computer to power off 4.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.433
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.228
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.116
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.328
When the network is plugged 0.076
And Tor is ready 18.378
Then the Upgrader considers the system as up-to-date 0.310
# 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.179
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:330 0.728
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.680
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 10.695
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.126
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 17.424
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.874
After features/support/hooks.rb:330 1.393
After features/support/hooks.rb:100 0.000