Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 10 31 Mar 2025, 18:52

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:45.937 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:27.742
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 53.322
When I start Tails from USB drive "old" with network unplugged 1:28.612
Then the boot device has safe access rights 3.436
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:330 7.210
After features/support/hooks.rb:100 0.011
Tags: @product
2:12.353
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login 1:27.344
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 32.736
And I take note of which tps features are available 2.118
Then a Tails persistence partition exists on USB drive "old" 0.908
And I shutdown Tails and wait for the computer to power off 8.641
After features/support/hooks.rb:330 0.228
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.452
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.043
Then Tails is running from USB drive "old" 1.846
And all tps features are active 1.994
When I write some files expected to persist 4.824
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 3.099
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 4.380
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.030
After features/support/hooks.rb:330 0.156
After features/support/hooks.rb:100 0.007
Tags: @product
2:45.750
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.466
And I log in to a new session 19.860
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.839
And I plug USB drive "to_upgrade" 2.498
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.220
Then the running Tails is installed on USB drive "to_upgrade" 32.393
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:330 1.043
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 1.773
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.635
Then all tps features from the old Tails version are active 1.760
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.556
And the expected persistent files created with the old Tails version are present in the filesystem 1.453
And all persistent directories from the old Tails version have safe access rights 2.495
After features/support/hooks.rb:330 1.461
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:10.820
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 41.375
And no SquashFS delta is installed 0.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
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.335
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.085
And Tor is ready 24.758
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.320
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.484
Given I shutdown Tails and wait for the computer to power off 11.655
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.467
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.381
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.293
# 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.305
When the network is plugged 0.078
And Tor is ready 18.452
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.610
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.785
Given I shutdown Tails and wait for the computer to power off 4.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.917
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.043
And the file system changes introduced in version 6.3~testoverlayfs are present 0.481
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.371
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.079
And Tor is ready 18.309
Then the Upgrader considers the system as up-to-date 0.309
# 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 14.599
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.168
After features/support/hooks.rb:330 0.788
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
39.786
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.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 19.850
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.094
After features/support/hooks.rb:330 1.404
After features/support/hooks.rb:100 0.000