Project Number Date
test_Tails_ISO_devel 3596 22 Nov 2024, 12:54

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 81 1 5 0 0 87 6 1 7 20:0.639 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:22.297
Before features/support/hooks.rb:269 0.006
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.937
When I start Tails from USB drive "old" with network unplugged 1:45.753
Then the boot device has safe access rights 3.237
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 9.721
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.931
Before features/support/hooks.rb:269 0.006
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login 1:26.662
Then Tails is running from USB drive "old" 0.422
And I create a persistent partition 30.688
And I take note of which tps features are available 2.180
Then a Tails persistence partition exists on USB drive "old" 0.897
And I shutdown Tails and wait for the computer to power off 6.844
After features/support/hooks.rb:326 0.256
After features/support/hooks.rb:100 0.009
Tags: @product
3:3.168
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.751
Then Tails is running from USB drive "old" 0.644
And all tps features are active 3.847
When I write some files expected to persist 1.824
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.910
And I take note of which tps features are available 0.953
And I shutdown Tails and wait for the computer to power off 4.826
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.553
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.914
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 14.032
And I log in to a new session 23.320
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.005
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.840
Then the running Tails is installed on USB drive "to_upgrade" 25.881
And I unplug USB drive "to_upgrade" 0.655
And I unplug USB drive "__internal" 0.697
After features/support/hooks.rb:326 3.875
After features/support/hooks.rb:100 0.000
Tags: @product
1:40.464
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 1.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:39.365
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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:326 4.940 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:50:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3596/artifact/build-artifacts/01:50:38_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3596/artifact/build-artifacts/01:50:38_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3596/artifact/build-artifacts/01:50:38_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3596/artifact/build-artifacts/01:50:38_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:23.199
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.832
And no SquashFS delta is installed 0.168
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.083
And Tor is ready 23.454
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.978
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.725
Given I shutdown Tails and wait for the computer to power off 11.729
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.751
Then Tails is running version 6.2~testoverlayfs 0.104
And all tps features are active 3.278
And the file system changes introduced in version 6.2~testoverlayfs are present 0.350
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.315
When the network is plugged 0.069
And Tor is ready 49.531
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.620
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.487
Given I shutdown Tails and wait for the computer to power off 4.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.148
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 3.032
And the file system changes introduced in version 6.3~testoverlayfs are present 0.610
And only the 6.3~testoverlayfs SquashFS delta is installed 0.119
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.413
When the network is plugged 0.081
And Tor is ready 21.637
Then the Upgrader considers the system as up-to-date 0.350
# 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.731
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.175
After features/support/hooks.rb:326 0.752
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
37.663
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.576
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.538
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.912
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 19.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.512
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.000