Project Number Date
test_Tails_ISO_21014-htpdateerror 19 01 Jul 2025, 23:11

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 27:8.829 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:58.090
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 41.143
When I start Tails from USB drive "old" with network unplugged 2:7.824
Then the boot device has safe access rights 6.613
And Tails is running from USB drive "old" 0.457
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 7.415
After features/support/hooks.rb:100 0.015
Tags: @product
2:57.415
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:58.496
Then Tails is running from USB drive "old" 0.509
And I create a persistent partition 41.623
And I take note of which tps features are available 4.150
Then a Tails persistence partition exists on USB drive "old" 3.426
And I shutdown Tails and wait for the computer to power off 8.992
After features/support/hooks.rb:330 0.272
After features/support/hooks.rb:100 0.016
Tags: @product
4:5.423
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:11.324
Then Tails is running from USB drive "old" 1.379
And all tps features are active 2.767
When I write some files expected to persist 1.844
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 3.241
And I take note of which tps features are available 0.653
And I shutdown Tails and wait for the computer to power off 7.903
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.395
After features/support/hooks.rb:330 1.758
After features/support/hooks.rb:100 0.025
Tags: @product
3:15.809
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.437
And I log in to a new session 26.298
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.835
And I plug USB drive "to_upgrade" 2.621
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.876
Then the running Tails is installed on USB drive "to_upgrade" 38.291
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:330 3.217
After features/support/hooks.rb:100 0.000
Tags: @product
3:11.863
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.138
Given a computer 0.370
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:54.805
Then all tps features from the old Tails version are active 2.106
And Tails is running from USB drive "to_upgrade" 1.972
And the boot device has safe access rights 8.575
And the expected persistent files created with the old Tails version are present in the filesystem 1.576
And all persistent directories from the old Tails version have safe access rights 2.457
After features/support/hooks.rb:330 2.263
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
9:36.404
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 17.351
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.220
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.514
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.921
When the network is plugged 0.122
And Tor is ready 37.605
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.020
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.278
Given I shutdown Tails and wait for the computer to power off 16.557
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:52.765
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.658
And the file system changes introduced in version 6.2~testoverlayfs are present 0.493
And only the 6.2~testoverlayfs SquashFS delta is installed 0.223
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.448
# 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.085
And Tor is ready 35.836
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 11.529
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.874
Given I shutdown Tails and wait for the computer to power off 9.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:47.189
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.350
And the file system changes introduced in version 6.3~testoverlayfs are present 0.777
And only the 6.3~testoverlayfs SquashFS delta is installed 0.158
# 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.365
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.403
When the network is plugged 0.099
And Tor is ready 32.797
Then the Upgrader considers the system as up-to-date 0.379
# 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.504
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.915
After features/support/hooks.rb:330 0.687
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
1:3.822
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 16.998
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the signing key used by the Upgrader is outdated 0.120
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 38.854
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.268
After features/support/hooks.rb:330 0.752
After features/support/hooks.rb:100 0.000