Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 15 05 Apr 2025, 19:16

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:4.051 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:5.010
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.080
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.130
When I start Tails from USB drive "old" with network unplugged 1:29.163
Then the boot device has safe access rights 3.286
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.120
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:330 7.242
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:24.674
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 29.975
And I take note of which tps features are available 2.274
Then a Tails persistence partition exists on USB drive "old" 0.767
And I shutdown Tails and wait for the computer to power off 8.246
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.007
Tags: @product
2:56.153
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 "old" with network unplugged and I login with persistence enabled 2:17.785
Then Tails is running from USB drive "old" 0.325
And all tps features are active 2.020
When I write some files expected to persist 1.594
# 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.410
And all persistent directories from the old Tails version have safe access rights 2.581
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 6.563
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.982
After features/support/hooks.rb:330 0.118
After features/support/hooks.rb:100 0.006
Tags: @product
2:29.876
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 without a persistent partition and stopped at Tails Greeter's login screen 10.383
And I log in to a new session 19.593
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.654
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.760
Then the running Tails is installed on USB drive "to_upgrade" 21.652
And I unplug USB drive "to_upgrade" 0.246
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 2.020
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.006
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.250
Then all tps features from the old Tails version are active 1.741
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.539
And the expected persistent files created with the old Tails version are present in the filesystem 1.436
And all persistent directories from the old Tails version have safe access rights 2.537
After features/support/hooks.rb:330 1.088
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.188
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 11.461
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.428
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.088
And Tor is ready 22.847
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.435
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.342
Given I shutdown Tails and wait for the computer to power off 8.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.559
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.402
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.277
When the network is plugged 0.074
And Tor is ready 19.115
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.986
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.040
Given I shutdown Tails and wait for the computer to power off 4.578
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.727
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.108
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.079
And Tor is ready 20.650
Then the Upgrader considers the system as up-to-date 0.312
# 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.956
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.399
After features/support/hooks.rb:330 0.693
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
38.312
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.302
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
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.089
And Tor is ready 21.263
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.156
After features/support/hooks.rb:330 0.879
After features/support/hooks.rb:100 0.000