Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 40 24 Aug 2024, 16:20

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:32.405 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:11.238
Before features/support/hooks.rb:269 0.007
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.552
When I start Tails from USB drive "old" with network unplugged 1:34.380
Then the boot device has safe access rights 3.003
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.532
After features/support/hooks.rb:100 0.010
Tags: @product
2:0.947
Before features/support/hooks.rb:269 0.007
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:18.911
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 30.983
And I take note of which tps features are available 1.531
Then a Tails persistence partition exists on USB drive "old" 0.794
And I shutdown Tails and wait for the computer to power off 8.196
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.010
Tags: @product
2:48.135
Before features/support/hooks.rb:269 0.007
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.576
Then Tails is running from USB drive "old" 0.368
And all tps features are active 1.801
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.220
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 2.332
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.200
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.598
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.491
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.257
And I log in to a new session 19.797
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.684
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.186
Then the running Tails is installed on USB drive "to_upgrade" 17.743
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 3.637
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.009
Before features/support/hooks.rb:269 0.008
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.485
Then all tps features from the old Tails version are active 2.284
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.024
And the expected persistent files created with the old Tails version are present in the filesystem 1.356
And all persistent directories from the old Tails version have safe access rights 2.337
After features/support/hooks.rb:326 0.852
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:1.764
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.948
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.675
When the network is plugged 0.074
And Tor is ready 48.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.614
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.742
Given I shutdown Tails and wait for the computer to power off 10.891
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.238
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.138
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.251
When the network is plugged 0.089
And Tor is ready 21.389
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.520
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.562
Given I shutdown Tails and wait for the computer to power off 4.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.906
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.035
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.374
When the network is plugged 0.067
And Tor is ready 44.452
Then the Upgrader considers the system as up-to-date 0.328
# 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 13.446
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.109
After features/support/hooks.rb:326 0.771
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
38.818
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.697
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.803
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 20.439
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.598
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.000