Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 23 14 Apr 2025, 18:49

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 22:13.379 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:29.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.216
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.730
When I start Tails from USB drive "old" with network unplugged 1:52.467
Then the boot device has safe access rights 3.535
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.314
After features/support/hooks.rb:330 3.831
After features/support/hooks.rb:100 0.010
Tags: @product
2:21.913
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.257
And I start Tails from USB drive "old" with network unplugged and I login 1:34.090
Then Tails is running from USB drive "old" 0.412
And I create a persistent partition 35.607
And I take note of which tps features are available 1.885
Then a Tails persistence partition exists on USB drive "old" 0.927
And I shutdown Tails and wait for the computer to power off 8.732
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.896
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.542
Then Tails is running from USB drive "old" 0.396
And all tps features are active 2.209
When I write some files expected to persist 1.838
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 2.901
And I take note of which tps features are available 0.506
And I shutdown Tails and wait for the computer to power off 4.467
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.114
After features/support/hooks.rb:330 0.123
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.519
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 without a persistent partition and stopped at Tails Greeter's login screen 11.658
And I log in to a new session 23.594
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.249
And I plug USB drive "to_upgrade" 2.523
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.982
Then the running Tails is installed on USB drive "to_upgrade" 27.868
And I unplug USB drive "to_upgrade" 0.335
And I unplug USB drive "__internal" 0.309
After features/support/hooks.rb:330 0.940
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.092
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.336
Then all tps features from the old Tails version are active 1.893
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.911
And the expected persistent files created with the old Tails version are present in the filesystem 1.779
And all persistent directories from the old Tails version have safe access rights 2.597
After features/support/hooks.rb:330 0.859
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
8:18.751
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 26.875
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.436
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.386
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.638
And Tor is ready 23.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.861
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.542
Given I shutdown Tails and wait for the computer to power off 11.101
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.751
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 3.067
And the file system changes introduced in version 6.2~testoverlayfs are present 0.474
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.384
# 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.432
When the network is plugged 0.113
And Tor is ready 24.589
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.580
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.436
Given I shutdown Tails and wait for the computer to power off 4.910
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.069
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 7.438
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.383
When the network is plugged 0.662
And Tor is ready 48.180
Then the Upgrader considers the system as up-to-date 0.317
# 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.687
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.740
After features/support/hooks.rb:330 0.873
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
43.950
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.149
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the signing key used by the Upgrader is outdated 0.138
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 20.466
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.629
After features/support/hooks.rb:330 1.302
After features/support/hooks.rb:100 0.000