Project Number Date
test_Tails_ISO_21014-htpdateerror 18 30 Jun 2025, 23:17

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 26:48.470 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:47.785
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 39.776
When I start Tails from USB drive "old" with network unplugged 2:1.895
Then the boot device has safe access rights 3.759
And Tails is running from USB drive "old" 0.399
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 4.337
After features/support/hooks.rb:100 0.088
Tags: @product
2:51.615
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.045
Given a computer 0.440
And I start Tails from USB drive "old" with network unplugged and I login 1:54.593
Then Tails is running from USB drive "old" 0.402
And I create a persistent partition 42.913
And I take note of which tps features are available 3.493
Then a Tails persistence partition exists on USB drive "old" 1.187
And I shutdown Tails and wait for the computer to power off 8.584
After features/support/hooks.rb:330 0.245
After features/support/hooks.rb:100 0.009
Tags: @product
4:15.392
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:16.569
Then Tails is running from USB drive "old" 0.635
And all tps features are active 2.006
When I write some files expected to persist 2.281
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.330
And all persistence configuration files have safe access rights 0.545
And all persistent directories from the old Tails version have safe access rights 5.753
And I take note of which tps features are available 1.237
And I shutdown Tails and wait for the computer to power off 7.747
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.009
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.011
Tags: @product
3:10.852
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 14.794
And I log in to a new session 28.112
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.042
And I plug USB drive "to_upgrade" 2.644
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.774
Then the running Tails is installed on USB drive "to_upgrade" 33.218
And I unplug USB drive "to_upgrade" 0.555
And I unplug USB drive "__internal" 0.709
After features/support/hooks.rb:330 4.602
After features/support/hooks.rb:100 0.000
Tags: @product
3:24.674
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Given a computer 0.665
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:4.055
Then all tps features from the old Tails version are active 2.204
And Tails is running from USB drive "to_upgrade" 0.386
And the boot device has safe access rights 5.049
And the expected persistent files created with the old Tails version are present in the filesystem 5.492
And all persistent directories from the old Tails version have safe access rights 6.820
After features/support/hooks.rb:330 0.884
After features/support/hooks.rb:100 0.012
9:25.924
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.575
And no SquashFS delta is installed 0.291
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.595
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.083
And Tor is ready 38.103
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.655
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.976
Given I shutdown Tails and wait for the computer to power off 16.728
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:3.471
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 6.391
And the file system changes introduced in version 6.2~testoverlayfs are present 1.022
And only the 6.2~testoverlayfs SquashFS delta is installed 0.242
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.561
# 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.615
When the network is plugged 0.147
And Tor is ready 23.421
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.229
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 18.268
Given I shutdown Tails and wait for the computer to power off 9.219
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:35.813
Then Tails is running version 6.3~testoverlayfs 0.551
And all tps features are active 5.503
And the file system changes introduced in version 6.3~testoverlayfs are present 0.716
And only the 6.3~testoverlayfs SquashFS delta is installed 0.119
# 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.374
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.692
When the network is plugged 0.070
And Tor is ready 24.101
Then the Upgrader considers the system as up-to-date 0.528
# 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 21.385
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.578
After features/support/hooks.rb:330 0.655
After features/support/hooks.rb:100 0.015
52.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.438
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.367
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.092
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 29.456
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.685
After features/support/hooks.rb:330 1.147
After features/support/hooks.rb:100 0.000