Project Number Date
test_Tails_ISO_devel 3419 06 Jun 2024, 12:48

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 38:34.247 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
1:54.109
Before features/support/hooks.rb:269 0.007
Given a computer 0.254
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.887
When I start Tails from USB drive "old" with network unplugged 1:17.954
Then the boot device has safe access rights 2.914
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:315 6.781
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.017
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:19.563
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 36.252
And I take note of which tps features are available 1.533
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.333
After features/support/hooks.rb:315 0.215
After features/support/hooks.rb:100 0.011
Tags: @product
22:0.038
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.007
Steps
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 21:59.827
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:713:in `new'
./features/step_definitions/common_steps.rb:713:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:296: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:315 10.833 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:04:01)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3419/artifact/build-artifacts/02:04:01_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/3419/artifact/build-artifacts/02:04:01_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3419/artifact/build-artifacts/02:04:01_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.013
Tags: @product
2:27.675
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.515
And I log in to a new session 17.867
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.189
And I plug USB drive "to_upgrade" 2.493
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.870
Then the running Tails is installed on USB drive "to_upgrade" 17.340
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:315 2.512
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.017
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.008
Steps
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.026
Then all tps features from the old Tails version are active 1.589
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.747
And the expected persistent files created with the old Tails version are present in the filesystem 0.071
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:21: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:315 5.262 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:08:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3419/artifact/build-artifacts/02:08:54_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/3419/artifact/build-artifacts/02:08:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3419/artifact/build-artifacts/02:08:54_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/3419/artifact/build-artifacts/02:08:54_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
7:15.346
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 30.247
And no SquashFS delta is installed 0.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.041
And Tor is ready 22.973
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.091
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.354
Given I shutdown Tails and wait for the computer to power off 9.473
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.816
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.378
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.412
# 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.298
When the network is plugged 0.037
And Tor is ready 18.950
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.858
Given I shutdown Tails and wait for the computer to power off 4.602
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.297
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.061
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.050
And Tor is ready 19.291
Then the Upgrader considers the system as up-to-date 0.337
# 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.571
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.884
After features/support/hooks.rb:315 0.795
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
38.042
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.943
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 1.331
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 19.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.435
After features/support/hooks.rb:315 0.978
After features/support/hooks.rb:100 0.000