Project Number Date
test_Tails_ISO_21014-htpdateerror 22 04 Jul 2025, 23:06

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 26:37.102 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:55.684
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.314
And I create a 7200 MiB disk named "old" 0.248
And I plug USB drive "old" 1.317
And I write an old version of the Tails USB image to disk "old" 47.037
When I start Tails from USB drive "old" with network unplugged 2:2.464
Then the boot device has safe access rights 3.167
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.374
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:330 3.805
After features/support/hooks.rb:100 0.010
Tags: @product
3:6.045
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 2:2.769
Then Tails is running from USB drive "old" 1.647
And I create a persistent partition 43.817
And I take note of which tps features are available 3.194
Then a Tails persistence partition exists on USB drive "old" 0.901
And I shutdown Tails and wait for the computer to power off 13.518
After features/support/hooks.rb:330 0.411
After features/support/hooks.rb:100 0.039
Tags: @product
4:10.462
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Given a computer 0.546
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:14.412
Then Tails is running from USB drive "old" 1.726
And all tps features are active 4.867
When I write some files expected to persist 2.202
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.405
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 2.815
And I take note of which tps features are available 0.486
And I shutdown Tails and wait for the computer to power off 6.782
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.772
After features/support/hooks.rb:330 0.297
After features/support/hooks.rb:100 0.028
Tags: @product
3:12.251
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.798
And I log in to a new session 22.685
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.392
And I plug USB drive "to_upgrade" 3.294
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.435
Then the running Tails is installed on USB drive "to_upgrade" 34.790
And I unplug USB drive "to_upgrade" 0.296
And I unplug USB drive "__internal" 0.559
After features/support/hooks.rb:330 2.818
After features/support/hooks.rb:100 0.000
Tags: @product
3:16.988
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.244
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:0.587
Then all tps features from the old Tails version are active 2.049
And Tails is running from USB drive "to_upgrade" 0.425
And the boot device has safe access rights 4.089
And the expected persistent files created with the old Tails version are present in the filesystem 5.305
And all persistent directories from the old Tails version have safe access rights 4.286
After features/support/hooks.rb:330 1.290
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
9:2.228
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 19.435
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.474
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.493
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.509
When the network is plugged 0.071
And Tor is ready 34.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.405
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.552
Given I shutdown Tails and wait for the computer to power off 15.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:52.463
Then Tails is running version 6.2~testoverlayfs 0.027
And all tps features are active 7.041
And the file system changes introduced in version 6.2~testoverlayfs are present 1.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.173
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.579
# 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.669
When the network is plugged 0.175
And Tor is ready 23.653
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.778
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.834
Given I shutdown Tails and wait for the computer to power off 8.200
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:34.168
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 5.096
And the file system changes introduced in version 6.3~testoverlayfs are present 1.733
And only the 6.3~testoverlayfs SquashFS delta is installed 0.286
# 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.718
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.870
When the network is plugged 0.341
And Tor is ready 21.702
Then the Upgrader considers the system as up-to-date 0.357
# 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.559
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.799
After features/support/hooks.rb:330 0.764
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
53.441
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 15.958
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.814
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.161
And the signing key used by the Upgrader is outdated 0.093
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 27.283
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.048
After features/support/hooks.rb:330 1.159
After features/support/hooks.rb:100 0.000