Project Number Date
test_Tails_ISO_21014-htpdateerror 27 09 Jul 2025, 02:40

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 18:56.239 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
1:54.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.193
When I start Tails from USB drive "old" with network unplugged 1:19.455
Then the boot device has safe access rights 3.126
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 6.867
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.090
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:27.671
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 32.788
And I take note of which tps features are available 2.279
Then a Tails persistence partition exists on USB drive "old" 1.014
And I shutdown Tails and wait for the computer to power off 8.766
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.918
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.061
Then Tails is running from USB drive "old" 0.397
And all tps features are active 2.091
When I write some files expected to persist 1.994
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.255
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.504
After features/support/hooks.rb:330 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.630
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.395
And I log in to a new session 17.698
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.788
And I plug USB drive "to_upgrade" 2.528
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.235
Then the running Tails is installed on USB drive "to_upgrade" 21.586
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:330 0.842
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.627
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.249
Then all tps features from the old Tails version are active 1.680
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.339
And the expected persistent files created with the old Tails version are present in the filesystem 1.519
And all persistent directories from the old Tails version have safe access rights 2.298
After features/support/hooks.rb:330 1.313
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:34.275
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.130
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.390
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.531
When the network is plugged 0.074
And Tor is ready 20.525
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.671
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.801
Given I shutdown Tails and wait for the computer to power off 8.760
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.636
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.368
And the file system changes introduced in version 6.2~testoverlayfs are present 0.397
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.272
When the network is plugged 0.080
And Tor is ready 17.139
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.012
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.220
Given I shutdown Tails and wait for the computer to power off 4.731
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.191
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.008
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.112
# 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.318
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 21.115
Then the Upgrader considers the system as up-to-date 0.302
# 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.945
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.658
After features/support/hooks.rb:330 0.759
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
34.545
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 9.708
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 17.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.069
After features/support/hooks.rb:330 1.184
After features/support/hooks.rb:100 0.000