Project Number Date
test_Tails_ISO_stable 5111 23 Sep 2024, 12:50

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 38:36.595 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:5.734
Before features/support/hooks.rb:269 0.004
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.090
When I start Tails from USB drive "old" with network unplugged 1:30.257
Then the boot device has safe access rights 3.126
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 6.931
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.470
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:24.057
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 31.586
And I take note of which tps features are available 1.390
Then a Tails persistence partition exists on USB drive "old" 0.731
And I shutdown Tails and wait for the computer to power off 8.211
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.950
Before features/support/hooks.rb:269 0.004
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.412
Then Tails is running from USB drive "old" 0.341
And all tps features are active 1.918
When I write some files expected to persist 1.802
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.512
And all persistent directories from the old Tails version have safe access rights 2.440
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 4.368
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.217
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.584
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.748
And I log in to a new session 20.414
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.507
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.731
Then the running Tails is installed on USB drive "to_upgrade" 17.374
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 2.949
After features/support/hooks.rb:100 0.000
Tags: @product
21:53.502
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 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 21:53.311
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55: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/common_steps.rb:715:in `new'
./features/step_definitions/common_steps.rb:715:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:301: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 10.806 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:03:24)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5111/artifact/build-artifacts/02:03:24_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5111/artifact/build-artifacts/02:03:24_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5111/artifact/build-artifacts/02:03:24_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:29.380
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 11.826
And no SquashFS delta is installed 0.164
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.171
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.068
And Tor is ready 21.058
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.302
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.653
Given I shutdown Tails and wait for the computer to power off 15.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.786
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.245
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.263
When the network is plugged 0.077
And Tor is ready 17.440
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.832
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.785
Given I shutdown Tails and wait for the computer to power off 6.392
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.797
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.140
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.103
And Tor is ready 19.455
Then the Upgrader considers the system as up-to-date 0.333
# 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.054
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.080
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
37.971
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 12.337
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 2.138
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 16.464
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.568
After features/support/hooks.rb:326 0.850
After features/support/hooks.rb:100 0.000