Project Number Date
test_Tails_ISO_21014-htpdateerror 23 05 Jul 2025, 23:35

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:14.476 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:51.195
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.456
And I create a 7200 MiB disk named "old" 0.079
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 41.860
When I start Tails from USB drive "old" with network unplugged 2:2.475
Then the boot device has safe access rights 3.915
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.540
After features/support/hooks.rb:330 6.236
After features/support/hooks.rb:100 0.012
Tags: @product
2:53.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:54.094
Then Tails is running from USB drive "old" 0.838
And I create a persistent partition 44.965
And I take note of which tps features are available 3.428
Then a Tails persistence partition exists on USB drive "old" 0.886
And I shutdown Tails and wait for the computer to power off 8.664
After features/support/hooks.rb:330 0.689
After features/support/hooks.rb:100 0.300
Tags: @product
4:38.152
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.124
Given a computer 1.318
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:31.794
Then Tails is running from USB drive "old" 0.633
And all tps features are active 3.042
When I write some files expected to persist 1.996
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.518
And all persistence configuration files have safe access rights 1.758
And all persistent directories from the old Tails version have safe access rights 8.189
And I take note of which tps features are available 0.596
And I shutdown Tails and wait for the computer to power off 4.434
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 43.869
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
3:20.290
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 17.682
And I log in to a new session 35.416
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.301
And I plug USB drive "to_upgrade" 2.541
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.892
Then the running Tails is installed on USB drive "to_upgrade" 34.015
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 3.292
After features/support/hooks.rb:100 0.000
Tags: @product
3:6.511
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given a computer 0.357
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:49.400
Then all tps features from the old Tails version are active 1.853
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.690
And the expected persistent files created with the old Tails version are present in the filesystem 4.835
And all persistent directories from the old Tails version have safe access rights 6.036
After features/support/hooks.rb:330 1.384
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
8:37.167
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.389
And no SquashFS delta is installed 0.196
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.853
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.307
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.817
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.675
When the network is plugged 0.073
And Tor is ready 24.373
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.353
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.863
Given I shutdown Tails and wait for the computer to power off 10.092
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:36.421
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.220
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.535
# 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.508
When the network is plugged 0.087
And Tor is ready 22.680
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.769
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.898
Given I shutdown Tails and wait for the computer to power off 8.845
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:43.696
Then Tails is running version 6.3~testoverlayfs 0.031
And all tps features are active 2.158
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.374
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.338
When the network is plugged 0.079
And Tor is ready 24.088
Then the Upgrader considers the system as up-to-date 0.402
# 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 25.554
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.558
After features/support/hooks.rb:330 0.894
After features/support/hooks.rb:100 0.051
Tags: @product @automatic_upgrade
48.063
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.479
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.838
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.399
And the signing key used by the Upgrader is outdated 1.624
But a current signing key is available on our website 0.000
When the network is plugged 0.504
And Tor is ready 26.136
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.081
After features/support/hooks.rb:330 0.853
After features/support/hooks.rb:100 0.000