Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 12 02 Apr 2025, 19:53

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:33.828 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:16.652
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 31.493
When I start Tails from USB drive "old" with network unplugged 1:39.503
Then the boot device has safe access rights 3.240
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 3.788
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:22.484
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 38.319
And I take note of which tps features are available 2.179
Then a Tails persistence partition exists on USB drive "old" 0.980
And I shutdown Tails and wait for the computer to power off 11.240
After features/support/hooks.rb:330 0.158
After features/support/hooks.rb:100 0.011
Tags: @product
3:8.966
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.430
Then Tails is running from USB drive "old" 0.439
And all tps features are active 2.064
When I write some files expected to persist 2.024
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 3.214
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 6.396
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.049
After features/support/hooks.rb:330 0.101
After features/support/hooks.rb:100 0.007
Tags: @product
2:39.649
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.507
And I log in to a new session 19.791
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.921
And I plug USB drive "to_upgrade" 2.527
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.773
Then the running Tails is installed on USB drive "to_upgrade" 28.669
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:330 1.957
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.658
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.811
Then all tps features from the old Tails version are active 1.744
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.433
And the expected persistent files created with the old Tails version are present in the filesystem 1.687
And all persistent directories from the old Tails version have safe access rights 2.436
After features/support/hooks.rb:330 2.160
After features/support/hooks.rb:100 0.009
7:10.887
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 16.071
And no SquashFS delta is installed 0.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.399
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.091
And Tor is ready 21.618
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.483
Given I shutdown Tails and wait for the computer to power off 8.675
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.653
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.342
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
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.335
# 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.292
When the network is plugged 0.104
And Tor is ready 48.492
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.606
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.120
Given I shutdown Tails and wait for the computer to power off 4.194
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.348
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.184
And the file system changes introduced in version 6.3~testoverlayfs are present 0.542
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.079
And Tor is ready 18.714
Then the Upgrader considers the system as up-to-date 0.316
# 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.102
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.544
After features/support/hooks.rb:330 0.776
After features/support/hooks.rb:100 0.017
39.236
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.565
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 0.124
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 21.051
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.826
After features/support/hooks.rb:330 1.155
After features/support/hooks.rb:100 0.000