Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 22 07 Nov 2024, 19:56

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 20:11.473 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:34.280
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.195
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.236
When I start Tails from USB drive "old" with network unplugged 2:1.754
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::SocketReadTimeout: execution expired
./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:89:in `new'
./features/support/helpers/dogtail.rb:89: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 5.295 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 01:32:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/22/artifact/build-artifacts/01:32:16_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/22/artifact/build-artifacts/01:32:16_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/22/artifact/build-artifacts/01:32:16_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/22/artifact/build-artifacts/01:32:16_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.991
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:28.327
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 32.629
And I take note of which tps features are available 1.627
Then a Tails persistence partition exists on USB drive "old" 1.255
And I shutdown Tails and wait for the computer to power off 8.617
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.007
Tags: @product
2:53.814
Before features/support/hooks.rb:269 0.005
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.231
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.453
When I write some files expected to persist 2.103
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 2.656
And I take note of which tps features are available 0.532
And I shutdown Tails and wait for the computer to power off 4.537
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.014
After features/support/hooks.rb:326 0.126
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.533
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.136
And I log in to a new session 19.233
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.478
And I plug USB drive "to_upgrade" 3.071
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.902
Then the running Tails is installed on USB drive "to_upgrade" 22.269
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 2.781
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.250
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.257
Then all tps features from the old Tails version are active 2.994
And Tails is running from USB drive "to_upgrade" 0.379
And the boot device has safe access rights 3.575
And the expected persistent files created with the old Tails version are present in the filesystem 1.502
And all persistent directories from the old Tails version have safe access rights 3.340
After features/support/hooks.rb:326 0.630
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:4.376
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.805
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.465
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.077
And Tor is ready 22.359
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.886
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.857
Given I shutdown Tails and wait for the computer to power off 8.891
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.177
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.644
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.109
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.436
# 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.323
When the network is plugged 0.082
And Tor is ready 19.430
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.970
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.977
Given I shutdown Tails and wait for the computer to power off 4.463
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.795
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.942
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.570
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.942
When the network is plugged 0.070
And Tor is ready 48.574
Then the Upgrader considers the system as up-to-date 0.327
# 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 15.404
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.983
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.226
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.483
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.754
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 20.920
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.804
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.000