Project Number Date
test_Tails_ISO_devel 3440 28 Jun 2024, 13:08

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:12.047 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:31.332
Before features/support/hooks.rb:269 0.005
Given a computer 0.258
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.354
When I start Tails from USB drive "old" with network unplugged 1:56.648
Then the boot device has safe access rights 2.986
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.727
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.559
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:28.123
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 32.062
And I take note of which tps features are available 1.415
Then a Tails persistence partition exists on USB drive "old" 0.862
And I shutdown Tails and wait for the computer to power off 8.543
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.010
Tags: @product
22:0.180
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 21:59.967
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:706:in `new'
./features/step_definitions/common_steps.rb:706:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:292: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:326 10.850 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:04:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3440/artifact/build-artifacts/02:04:56_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/3440/artifact/build-artifacts/02:04:56_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/3440/artifact/build-artifacts/02:04:56_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.031
Tags: @product
2:22.745
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 10.871
And I log in to a new session 16.816
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.295
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.355
Then the running Tails is installed on USB drive "to_upgrade" 17.525
And I unplug USB drive "to_upgrade" 0.266
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 2.499
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.515
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.007
Steps
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.063
Then all tps features from the old Tails version are active 1.726
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.107
And the expected persistent files created with the old Tails version are present in the filesystem 0.066
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:1081:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1080:in `each'
./features/step_definitions/usb.rb:1080: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:326 5.216 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:09:40)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3440/artifact/build-artifacts/02:09:40_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/3440/artifact/build-artifacts/02:09:40_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3440/artifact/build-artifacts/02:09:40_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/3440/artifact/build-artifacts/02:09:40_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:22.135
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.676
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.031
And Tor is ready 19.840
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.208
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.571
Given I shutdown Tails and wait for the computer to power off 10.938
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.152
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.485
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
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.467
# 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.278
When the network is plugged 0.039
And Tor is ready 19.901
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.041
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.616
Given I shutdown Tails and wait for the computer to power off 4.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.818
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.907
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.050
And Tor is ready 20.262
Then the Upgrader considers the system as up-to-date 0.328
# 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 13.591
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.870
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.577
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 10.708
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.430
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.766
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 17.972
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.607
After features/support/hooks.rb:326 1.058
After features/support/hooks.rb:100 0.000