Project Number Date
test_Tails_ISO_devel 3478 13 Aug 2024, 18:27

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:18.630 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:30.963
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.248
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.708
When I start Tails from USB drive "old" with network unplugged 1:56.905
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:454: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:453:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:287: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:453:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:287: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.358 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 01:42:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3478/artifact/build-artifacts/01:42:29_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_devel/3478/artifact/build-artifacts/01:42:29_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3478/artifact/build-artifacts/01:42:29_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3478/artifact/build-artifacts/01:42:29_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.013
Tags: @product
2:19.385
Before features/support/hooks.rb:269 0.010
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:31.776
Then Tails is running from USB drive "old" 0.443
And I create a persistent partition 35.710
And I take note of which tps features are available 1.865
Then a Tails persistence partition exists on USB drive "old" 0.887
And I shutdown Tails and wait for the computer to power off 8.458
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.568
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.935
Then Tails is running from USB drive "old" 0.384
And all tps features are active 2.085
When I write some files expected to persist 1.792
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.781
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.385
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.928
After features/support/hooks.rb:326 0.108
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.219
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.102
And I log in to a new session 23.313
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.917
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.755
Then the running Tails is installed on USB drive "to_upgrade" 23.199
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.282
After features/support/hooks.rb:326 2.664
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.462
Before features/support/hooks.rb:269 0.008
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.497
Then all tps features from the old Tails version are active 1.976
And Tails is running from USB drive "to_upgrade" 0.410
And the boot device has safe access rights 3.880
And the expected persistent files created with the old Tails version are present in the filesystem 1.675
And all persistent directories from the old Tails version have safe access rights 2.814
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:56.366
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 25.668
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
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.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.154
And Tor is ready 21.297
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.659
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.019
Given I shutdown Tails and wait for the computer to power off 8.946
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.871
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.508
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.308
When the network is plugged 0.071
And Tor is ready 18.252
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.491
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.533
Given I shutdown Tails and wait for the computer to power off 6.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.799
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.203
And the file system changes introduced in version 6.3~testoverlayfs are present 0.679
And only the 6.3~testoverlayfs SquashFS delta is installed 0.161
# 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.433
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.416
When the network is plugged 0.095
And Tor is ready 19.532
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 14.085
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.199
After features/support/hooks.rb:326 0.801
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
41.664
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.448
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 1.777
But a current signing key is available on our website 0.000
When the network is plugged 0.116
And Tor is ready 21.783
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.137
After features/support/hooks.rb:326 0.966
After features/support/hooks.rb:100 0.000