Project Number Date
test_Tails_ISO_21014-htpdateerror 5 16 Jun 2025, 23:21

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:48.404 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:39.137
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 39.847
When I start Tails from USB drive "old" with network unplugged 1:52.727
Then the boot device has safe access rights 3.951
And Tails is running from USB drive "old" 0.449
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.276
After features/support/hooks.rb:330 4.616
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.647
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:42.695
Then Tails is running from USB drive "old" 0.454
And I create a persistent partition 39.002
And I take note of which tps features are available 2.402
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 10.097
After features/support/hooks.rb:330 0.269
After features/support/hooks.rb:100 0.016
Tags: @product
3:24.838
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:38.374
Then Tails is running from USB drive "old" 1.601
And all tps features are active 2.393
When I write some files expected to persist 1.759
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.776
And I take note of which tps features are available 0.590
And I shutdown Tails and wait for the computer to power off 6.863
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.664
After features/support/hooks.rb:330 0.167
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.930
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.568
And I log in to a new session 24.944
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.799
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.274
Then the running Tails is installed on USB drive "to_upgrade" 36.415
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.281
After features/support/hooks.rb:330 4.392
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.580
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.567
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:29.401
Then all tps features from the old Tails version are active 2.650
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 3.627
And the expected persistent files created with the old Tails version are present in the filesystem 1.906
And all persistent directories from the old Tails version have safe access rights 3.059
After features/support/hooks.rb:330 1.849
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
7:46.012
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.801
And no SquashFS delta is installed 0.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.614
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.533
When the network is plugged 0.105
And Tor is ready 22.512
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.097
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.258
Given I shutdown Tails and wait for the computer to power off 11.436
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.832
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 5.919
And the file system changes introduced in version 6.2~testoverlayfs are present 0.467
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.462
When the network is plugged 0.069
And Tor is ready 21.806
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.613
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.895
Given I shutdown Tails and wait for the computer to power off 7.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.786
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.276
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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.498
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.277
When the network is plugged 0.094
And Tor is ready 22.703
Then the Upgrader considers the system as up-to-date 0.324
# 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 20.719
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.096
After features/support/hooks.rb:330 0.886
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
41.258
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.691
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.117
And Tor is ready 20.420
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.551
After features/support/hooks.rb:330 1.050
After features/support/hooks.rb:100 0.000