Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 17 07 Apr 2025, 18:43

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 21:47.097 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:15.069
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.252
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 32.344
When I start Tails from USB drive "old" with network unplugged 1:36.978
Then the boot device has safe access rights 3.214
And Tails is running from USB drive "old" 0.449
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:330 3.810
After features/support/hooks.rb:100 0.019
Tags: @product
2:21.615
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.273
And I start Tails from USB drive "old" with network unplugged and I login 1:36.247
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 32.517
And I take note of which tps features are available 2.081
Then a Tails persistence partition exists on USB drive "old" 0.972
And I shutdown Tails and wait for the computer to power off 9.185
After features/support/hooks.rb:330 0.235
After features/support/hooks.rb:100 0.014
Tags: @product
3:4.611
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.885
Then Tails is running from USB drive "old" 0.408
And all tps features are active 2.198
When I write some files expected to persist 2.041
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.503
And all persistent directories from the old Tails version have safe access rights 3.147
And I take note of which tps features are available 0.788
And I shutdown Tails and wait for the computer to power off 6.871
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.291
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.008
Tags: @product
2:39.420
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.241
And I log in to a new session 19.547
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.680
And I plug USB drive "to_upgrade" 2.489
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.484
Then the running Tails is installed on USB drive "to_upgrade" 26.512
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 7.322
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.255
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.908
Then all tps features from the old Tails version are active 3.238
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 3.265
And the expected persistent files created with the old Tails version are present in the filesystem 1.520
And all persistent directories from the old Tails version have safe access rights 2.452
After features/support/hooks.rb:330 1.582
After features/support/hooks.rb:100 0.008
8:19.005
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.365
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.525
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.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.108
And Tor is ready 22.856
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.600
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.390
Given I shutdown Tails and wait for the computer to power off 11.213
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.660
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 4.175
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.387
# 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.310
When the network is plugged 0.279
And Tor is ready 21.186
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.436
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.153
Given I shutdown Tails and wait for the computer to power off 1:1.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.027
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.988
And the file system changes introduced in version 6.3~testoverlayfs are present 0.658
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.362
When the network is plugged 0.178
And Tor is ready 15.972
Then the Upgrader considers the system as up-to-date 10.944
# 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.384
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.765
After features/support/hooks.rb:330 0.807
After features/support/hooks.rb:100 0.024
41.349
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 12.200
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.434
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.155
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.123
And Tor is ready 19.466
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.852
After features/support/hooks.rb:330 1.093
After features/support/hooks.rb:100 0.000