Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 4 16 Dec 2024, 20:32

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 80 1 6 0 0 87 6 1 7 21:30.061 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:36.820
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.102
And I write an old version of the Tails USB image to disk "old" 32.384
When I start Tails from USB drive "old" with network unplugged 2:3.090
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:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:326 6.095 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 01:33:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/4/artifact/build-artifacts/01:33:30_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/4/artifact/build-artifacts/01:33:30_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/4/artifact/build-artifacts/01:33:30_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/4/artifact/build-artifacts/01:33:30_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.785
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:40.039
Then Tails is running from USB drive "old" 0.441
And I create a persistent partition 33.382
And I take note of which tps features are available 1.886
Then a Tails persistence partition exists on USB drive "old" 0.954
And I shutdown Tails and wait for the computer to power off 8.876
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.012
Tags: @product
3:5.805
Before features/support/hooks.rb:269 0.008
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.593
Then Tails is running from USB drive "old" 0.998
And all tps features are active 2.072
When I write some files expected to persist 1.828
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
And all persistence configuration files have safe access rights 0.540
And all persistent directories from the old Tails version have safe access rights 2.934
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.381
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.434
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.012
Tags: @product
2:38.664
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 12.004
And I log in to a new session 20.771
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.713
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.957
Then the running Tails is installed on USB drive "to_upgrade" 22.345
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:326 3.741
After features/support/hooks.rb:100 0.000
Tags: @product
2:34.994
Before features/support/hooks.rb:269 0.008
Given a computer 0.266
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.490
Then all tps features from the old Tails version are active 2.671
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.939
And the expected persistent files created with the old Tails version are present in the filesystem 1.535
And all persistent directories from the old Tails version have safe access rights 2.737
After features/support/hooks.rb:326 1.142
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:21.411
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.735
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.338
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.087
And Tor is ready 20.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.265
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.616
Given I shutdown Tails and wait for the computer to power off 11.157
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.491
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 6.949
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.285
When the network is plugged 0.792
And Tor is ready 18.420
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.921
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.210
Given I shutdown Tails and wait for the computer to power off 4.501
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.412
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.470
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.358
When the network is plugged 0.101
And Tor is ready 19.250
Then the Upgrader considers the system as up-to-date 10.925
# 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.028
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.004
After features/support/hooks.rb:326 0.825
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
46.578
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.630
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.785
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 19.929
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.652
After features/support/hooks.rb:326 1.454
After features/support/hooks.rb:100 0.000