Project Number Date
test_Tails_ISO_stable 5254 07 Nov 2024, 20:06

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 1 11 0 0 87 6 1 7 39:12.657 Failed
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.670
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.603
When I start Tails from USB drive "old" with network unplugged 1:37.771
Then the boot device has safe access rights 3.037
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.513
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.351
Before features/support/hooks.rb:269 0.004
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:24.498
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 38.177
And I take note of which tps features are available 1.708
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 8.506
After features/support/hooks.rb:326 0.196
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.830
Before features/support/hooks.rb:269 0.004
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.252
Then Tails is running from USB drive "old" 0.336
And all tps features are active 2.096
When I write some files expected to persist 1.897
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.301
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.726
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 4.572
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.518
After features/support/hooks.rb:326 0.101
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.326
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.912
And I log in to a new session 22.201
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.684
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.359
Then the running Tails is installed on USB drive "to_upgrade" 22.254
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.295
After features/support/hooks.rb:326 3.925
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.748
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.604
Then all tps features from the old Tails version are active 2.021
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.852
And the expected persistent files created with the old Tails version are present in the filesystem 1.725
And all persistent directories from the old Tails version have safe access rights 3.000
After features/support/hooks.rb:326 0.825
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
26:4.204
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 33.436
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.595
When the network is plugged 0.155
And Tor is ready 27.856
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.887
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.427
Given I shutdown Tails and wait for the computer to power off 10.660
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.168
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.329
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# 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.269
When the network is plugged 0.082
And Tor is ready 17.779
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.743
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.578
Given I shutdown Tails and wait for the computer to power off 4.563
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:45.013
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:712:in `new'
./features/step_definitions/common_steps.rb:712:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:326 10.797 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:11:45)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5254/artifact/build-artifacts/02:11:45_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5254/artifact/build-artifacts/02:11:45_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5254/artifact/build-artifacts/02:11:45_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
43.525
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.574
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.800
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 23.648
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.924
After features/support/hooks.rb:326 1.306
After features/support/hooks.rb:100 0.000