Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 67 27 Dec 2024, 21:05

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 39:19.162 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:9.808
Before features/support/hooks.rb:269 0.006
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 33.568
When I start Tails from USB drive "old" with network unplugged 1:30.600
Then the boot device has safe access rights 3.174
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.264
After features/support/hooks.rb:326 3.537
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.919
Before features/support/hooks.rb:269 0.004
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:25.510
Then Tails is running from USB drive "old" 0.428
And I create a persistent partition 33.428
And I take note of which tps features are available 1.440
Then a Tails persistence partition exists on USB drive "old" 0.929
And I shutdown Tails and wait for the computer to power off 8.956
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.309
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 with persistence enabled 2:16.131
Then Tails is running from USB drive "old" 1.541
And all tps features are active 2.140
When I write some files expected to persist 1.929
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.671
And all persistence configuration files have safe access rights 0.490
And all persistent directories from the old Tails version have safe access rights 3.632
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.333
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.744
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.687
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 11.480
And I log in to a new session 22.970
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.574
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.332
Then the running Tails is installed on USB drive "to_upgrade" 24.468
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 2.375
After features/support/hooks.rb:100 0.000
Tags: @product
21:58.899
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 21:58.695
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:712:in `new'
./features/step_definitions/common_steps.rb:712:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298: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.832 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:03:55)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/67/artifact/build-artifacts/02:03:55_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/67/artifact/build-artifacts/02:03:55_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/67/artifact/build-artifacts/02:03:55_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:50.444
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 12.110
And no SquashFS delta is installed 0.251
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.365
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.107
And Tor is ready 47.361
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.580
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.518
Given I shutdown Tails and wait for the computer to power off 10.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.710
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.012
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.281
# 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.289
When the network is plugged 0.072
And Tor is ready 16.507
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.077
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.919
Given I shutdown Tails and wait for the computer to power off 4.238
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.772
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.080
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.111
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.083
And Tor is ready 15.300
Then the Upgrader considers the system as up-to-date 0.303
# 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.567
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.925
After features/support/hooks.rb:326 0.702
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.094
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 9.686
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 17.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.437
After features/support/hooks.rb:326 0.625
After features/support/hooks.rb:100 0.000