Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 22 22 Mar 2025, 21:47

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:17.732 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:6.958
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.317
When I start Tails from USB drive "old" with network unplugged 1:31.284
Then the boot device has safe access rights 3.049
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.232
After features/support/hooks.rb:330 3.483
After features/support/hooks.rb:100 0.037
Tags: @product
2:10.882
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:27.940
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 31.962
And I take note of which tps features are available 1.422
Then a Tails persistence partition exists on USB drive "old" 0.739
And I shutdown Tails and wait for the computer to power off 8.278
After features/support/hooks.rb:330 0.133
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.758
Then Tails is running from USB drive "old" 0.332
And all tps features are active 2.129
When I write some files expected to persist 1.926
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.373
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 4.256
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 22.851
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.551
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 10.583
And I log in to a new session 18.851
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.461
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.223
Then the running Tails is installed on USB drive "to_upgrade" 18.537
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:330 2.724
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.332
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.469
Then all tps features from the old Tails version are active 1.560
And Tails is running from USB drive "to_upgrade" 0.387
And the boot device has safe access rights 3.077
And the expected persistent files created with the old Tails version are present in the filesystem 1.434
And all persistent directories from the old Tails version have safe access rights 2.195
After features/support/hooks.rb:330 1.446
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:50.164
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 10.770
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.519
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.087
And Tor is ready 46.165
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.573
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.454
Given I shutdown Tails and wait for the computer to power off 8.470
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.432
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.191
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.118
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.282
When the network is plugged 0.080
And Tor is ready 21.268
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.912
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.209
Given I shutdown Tails and wait for the computer to power off 4.201
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.108
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.993
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.277
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.361
When the network is plugged 0.063
And Tor is ready 20.033
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 15.083
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.000
After features/support/hooks.rb:330 0.729
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
33.982
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.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.408
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.130
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 18.226
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.991
After features/support/hooks.rb:330 0.932
After features/support/hooks.rb:100 0.000