Project Number Date
test_Tails_ISO_21014-htpdateerror 28 15 Jul 2025, 01:48

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 20:18.753 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:14.203
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.690
When I start Tails from USB drive "old" with network unplugged 1:33.696
Then the boot device has safe access rights 5.033
And Tails is running from USB drive "old" 0.534
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.152
And udev-watchdog is monitoring the correct device 0.458
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:330 6.846
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.398
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:35.934
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 36.520
And I take note of which tps features are available 1.571
Then a Tails persistence partition exists on USB drive "old" 0.952
And I shutdown Tails and wait for the computer to power off 8.911
After features/support/hooks.rb:330 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.878
Then Tails is running from USB drive "old" 1.227
And all tps features are active 2.695
When I write some files expected to persist 3.191
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.859
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 6.492
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.473
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.031
Tags: @product
2:37.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.392
And I log in to a new session 19.489
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.449
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.059
Then the running Tails is installed on USB drive "to_upgrade" 29.734
And I unplug USB drive "to_upgrade" 0.429
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:330 2.927
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.577
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.039
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.200
Then all tps features from the old Tails version are active 1.741
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.375
And the expected persistent files created with the old Tails version are present in the filesystem 2.127
And all persistent directories from the old Tails version have safe access rights 2.590
After features/support/hooks.rb:330 1.193
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:53.836
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.227
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.372
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.406
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.067
And Tor is ready 23.807
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.820
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.491
Given I shutdown Tails and wait for the computer to power off 9.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.800
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.478
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
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.325
# 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.283
When the network is plugged 0.114
And Tor is ready 19.784
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.832
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.897
Given I shutdown Tails and wait for the computer to power off 4.772
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.470
Then Tails is running version 6.3~testoverlayfs 0.081
And all tps features are active 2.460
And the file system changes introduced in version 6.3~testoverlayfs are present 0.532
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.101
And Tor is ready 17.275
Then the Upgrader considers the system as up-to-date 0.335
# 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 16.209
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.770
After features/support/hooks.rb:330 1.211
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
41.256
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 10.422
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.144
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 22.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.895
After features/support/hooks.rb:330 0.977
After features/support/hooks.rb:100 0.000