Project Number Date
test_Tails_ISO_devel 3405 29 May 2024, 17:33

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 2 10 0 0 87 5 2 7 37:48.852 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:8.523
Before features/support/hooks.rb:259 0.005
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.105
When I start Tails from USB drive "old" with network unplugged 1:34.297
Then the boot device has safe access rights 2.894
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:305 7.806
After features/support/hooks.rb:89 0.013
Tags: @product
2:6.781
Before features/support/hooks.rb:259 0.008
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:20.102
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 35.358
And I take note of which tps features are available 1.392
Then a Tails persistence partition exists on USB drive "old" 0.875
And I shutdown Tails and wait for the computer to power off 8.509
After features/support/hooks.rb:305 0.151
After features/support/hooks.rb:89 0.011
Tags: @product
22:5.936
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:259 0.005
Steps
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 22:5.765
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:295: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:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:305 9.903 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:00:21)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:00:21_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:00:21_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
After features/support/hooks.rb:89 0.010
Tags: @product
2:25.414
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.013
And I log in to a new session 19.148
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.483
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.301
Then the running Tails is installed on USB drive "to_upgrade" 16.598
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.253
After features/support/hooks.rb:305 6.916
After features/support/hooks.rb:89 0.000
Tags: @product
2:14.209
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:259 0.007
Steps
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.588
Then all tps features from the old Tails version are active 1.519
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.570
And the expected persistent files created with the old Tails version are present in the filesystem 0.047
Could 
Could not find expected file in persistent directory /home/amnesia/Persistent.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/helpers/misc_helpers.rb:22:in `assert_vmcommand_success'
./features/step_definitions/usb.rb:1045:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1044:in `each'
./features/step_definitions/usb.rb:1044:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:305 4.307 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:05:17)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:05:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:05:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:05:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:05:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:13.904
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.595
And no SquashFS delta is installed 0.232
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.025
And Tor is ready 20.740
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.680
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.777
Given I shutdown Tails and wait for the computer to power off 8.524
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.200
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.024
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
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.329
# 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.247
When the network is plugged 0.028
And Tor is ready 19.912
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.686
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.136
Given I shutdown Tails and wait for the computer to power off 4.492
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.599
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.962
And the file system changes introduced in version 6.3~testoverlayfs are present 0.455
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.044
And Tor is ready 18.071
Then the Upgrader considers the system as up-to-date 0.342
# 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.700
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.955
After features/support/hooks.rb:305 0.692
After features/support/hooks.rb:89 0.065
Tags: @product @automatic_upgrade
34.081
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.432
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.957
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 15.088
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.152
After features/support/hooks.rb:305 0.984
After features/support/hooks.rb:89 0.000