Project Number Date
test_Tails_ISO_21014-htpdateerror 13 25 Jun 2025, 23: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 32:28.636 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
3:16.148
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 44.158
When I start Tails from USB drive "old" with network unplugged 2:19.185
Then the boot device has safe access rights 9.630
And Tails is running from USB drive "old" 0.955
And there is no persistence partition on USB drive "old" 0.147
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.414
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 3.785
After features/support/hooks.rb:100 0.009
Tags: @product
3:22.937
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login 2:15.441
Then Tails is running from USB drive "old" 0.568
And I create a persistent partition 45.728
And I take note of which tps features are available 2.942
Then a Tails persistence partition exists on USB drive "old" 6.158
And I shutdown Tails and wait for the computer to power off 11.886
After features/support/hooks.rb:330 0.372
After features/support/hooks.rb:100 0.056
Tags: @product
4:18.340
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.272
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:16.719
Then Tails is running from USB drive "old" 0.610
And all tps features are active 2.650
When I write some files expected to persist 4.263
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.849
And all persistence configuration files have safe access rights 1.303
And all persistent directories from the old Tails version have safe access rights 6.380
And I take note of which tps features are available 0.547
And I shutdown Tails and wait for the computer to power off 4.711
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 40.032
After features/support/hooks.rb:330 0.350
After features/support/hooks.rb:100 0.011
Tags: @product
3:34.865
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.691
And I log in to a new session 30.640
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.281
And I plug USB drive "to_upgrade" 2.710
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:3.107
Then the running Tails is installed on USB drive "to_upgrade" 33.980
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:330 1.879
After features/support/hooks.rb:100 0.000
Tags: @product
3:42.628
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:20.423
Then all tps features from the old Tails version are active 3.025
And Tails is running from USB drive "to_upgrade" 0.413
And the boot device has safe access rights 11.603
And the expected persistent files created with the old Tails version are present in the filesystem 3.680
And all persistent directories from the old Tails version have safe access rights 3.284
After features/support/hooks.rb:330 1.397
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
12:38.324
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 23.336
And no SquashFS delta is installed 3.960
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 3.843
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.674
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.143
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.812
When the network is plugged 0.094
And Tor is ready 42.858
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 17.580
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 21.727
Given I shutdown Tails and wait for the computer to power off 16.241
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:50.402
Then Tails is running version 6.2~testoverlayfs 0.099
And all tps features are active 9.711
And the file system changes introduced in version 6.2~testoverlayfs are present 1.194
And only the 6.2~testoverlayfs SquashFS delta is installed 0.157
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.490
# 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.394
When the network is plugged 0.098
And Tor is ready 36.657
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.603
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 22.082
Given I shutdown Tails and wait for the computer to power off 13.857
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:41.259
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.984
And the file system changes introduced in version 6.3~testoverlayfs are present 0.834
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.376
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.385
When the network is plugged 0.079
And Tor is ready 34.255
Then the Upgrader considers the system as up-to-date 0.323
# 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 39.957
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.748
After features/support/hooks.rb:330 1.022
After features/support/hooks.rb:100 0.098
Tags: @product @automatic_upgrade
1:35.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.030
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.005
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 5.052
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.804
And the signing key used by the Upgrader is outdated 1.391
But a current signing key is available on our website 0.000
When the network is plugged 0.850
And Tor is ready 1:1.562
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.724
After features/support/hooks.rb:330 1.191
After features/support/hooks.rb:100 0.000