Project Number Date
test_Tails_ISO_21014-htpdateerror 3 14 Jun 2025, 21:56

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 19:53.051 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:12.595
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.250
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.627
When I start Tails from USB drive "old" with network unplugged 1:35.573
Then the boot device has safe access rights 2.944
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.232
After features/support/hooks.rb:330 7.165
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.593
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:32.185
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 31.372
And I take note of which tps features are available 2.285
Then a Tails persistence partition exists on USB drive "old" 0.910
And I shutdown Tails and wait for the computer to power off 8.367
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.310
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 "old" with network unplugged and I login with persistence enabled 2:22.882
Then Tails is running from USB drive "old" 0.296
And all tps features are active 2.177
When I write some files expected to persist 1.875
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.455
And I take note of which tps features are available 0.476
And I shutdown Tails and wait for the computer to power off 4.444
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.868
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.006
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 without a persistent partition and stopped at Tails Greeter's login screen 9.964
And I log in to a new session 20.794
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.649
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.276
Then the running Tails is installed on USB drive "to_upgrade" 26.431
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:330 2.129
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.162
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.199
Then all tps features from the old Tails version are active 1.699
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.196
And the expected persistent files created with the old Tails version are present in the filesystem 1.409
And all persistent directories from the old Tails version have safe access rights 2.155
After features/support/hooks.rb:330 1.286
After features/support/hooks.rb:100 0.070
6:43.241
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 13.067
And no SquashFS delta is installed 0.924
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.086
And Tor is ready 21.962
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.637
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.087
Given I shutdown Tails and wait for the computer to power off 8.849
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.920
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.022
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.284
When the network is plugged 0.076
And Tor is ready 17.278
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.431
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.303
Given I shutdown Tails and wait for the computer to power off 4.662
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.842
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.101
And the file system changes introduced in version 6.3~testoverlayfs are present 0.550
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.087
And Tor is ready 19.666
Then the Upgrader considers the system as up-to-date 0.317
# 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 15.045
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.571
After features/support/hooks.rb:330 0.840
After features/support/hooks.rb:100 0.045
42.140
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 11.535
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.094
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 22.224
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.998
After features/support/hooks.rb:330 0.878
After features/support/hooks.rb:100 0.000