Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 88 26 Jan 2025, 20:56

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 63 1 23 0 0 87 6 1 7 15:25.122 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:23.242
Before features/support/hooks.rb:269 0.005
Given a computer 0.373
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 37.332
When I start Tails from USB drive "old" with network unplugged 1:40.228
Then the boot device has safe access rights 3.106
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:326 3.754
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.372
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:28.630
Then Tails is running from USB drive "old" 0.389
And I create a persistent partition 31.989
And I take note of which tps features are available 1.921
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 8.385
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.650
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.563
Then Tails is running from USB drive "old" 0.867
And all tps features are active 2.048
When I write some files expected to persist 1.856
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 3.081
And I take note of which tps features are available 0.542
And I shutdown Tails and wait for the computer to power off 4.319
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.536
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.372
Before features/support/hooks.rb:269 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 10.650
And I log in to a new session 18.752
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.626
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.269
Then the running Tails is installed on USB drive "to_upgrade" 21.270
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 6.688
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.954
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.312
Then all tps features from the old Tails version are active 1.772
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.503
And the expected persistent files created with the old Tails version are present in the filesystem 1.492
And all persistent directories from the old Tails version have safe access rights 2.354
After features/support/hooks.rb:326 0.632
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
2:35.962
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.898
And no SquashFS delta is installed 0.575
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.067
And Tor is ready 19.213
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.786
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.732
Given I shutdown Tails and wait for the computer to power off 8.688
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:35.876
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:451:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:450:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
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 5.082 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:41:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/88/artifact/build-artifacts/01:41:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/88/artifact/build-artifacts/01:41:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/88/artifact/build-artifacts/01:41:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/88/artifact/build-artifacts/01:41:57_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
34.567
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.881
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.672
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 16.345
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.444
After features/support/hooks.rb:326 1.064
After features/support/hooks.rb:100 0.000