Project Number Date
test_Tails_ISO_devel 3786 18 Apr 2025, 10:16

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 39:37.124 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:30.385
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.155
When I start Tails from USB drive "old" with network unplugged 1:53.272
Then the boot device has safe access rights 3.482
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.326
After features/support/hooks.rb:330 3.742
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.750
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:26.508
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 32.444
And I take note of which tps features are available 2.679
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 8.694
After features/support/hooks.rb:330 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
22:11.310
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 22:11.079
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:719:in `new'
./features/step_definitions/common_steps.rb:719: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: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:330 11.001 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:07:25)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3786/artifact/build-artifacts/02:07:25_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/3786/artifact/build-artifacts/02:07:25_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/3786/artifact/build-artifacts/02:07:25_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.012
Tags: @product
2:40.162
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.586
And I log in to a new session 21.814
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.789
And I plug USB drive "to_upgrade" 2.559
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.550
Then the running Tails is installed on USB drive "to_upgrade" 28.343
And I unplug USB drive "to_upgrade" 0.257
And I unplug USB drive "__internal" 0.262
After features/support/hooks.rb:330 1.315
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.861
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.371
Then all tps features from the old Tails version are active 1.842
And Tails is running from USB drive "to_upgrade" 0.424
And the boot device has safe access rights 3.948
And the expected persistent files created with the old Tails version are present in the filesystem 0.067
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:1097:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1096:in `each'
./features/step_definitions/usb.rb:1096: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:330 5.678 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:12:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3786/artifact/build-artifacts/02:12:35_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/3786/artifact/build-artifacts/02:12:35_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3786/artifact/build-artifacts/02:12:35_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/3786/artifact/build-artifacts/02:12:35_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:7.492
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.503
And no SquashFS delta is installed 0.380
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.716
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.524
When the network is plugged 0.073
And Tor is ready 23.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.072
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.975
Given I shutdown Tails and wait for the computer to power off 15.316
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.958
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.173
And the file system changes introduced in version 6.2~testoverlayfs are present 0.388
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.315
When the network is plugged 0.074
And Tor is ready 18.196
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.292
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.011
Given I shutdown Tails and wait for the computer to power off 4.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.144
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.335
And the file system changes introduced in version 6.3~testoverlayfs are present 0.672
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.407
When the network is plugged 0.069
And Tor is ready 20.185
Then the Upgrader considers the system as up-to-date 0.332
# 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 17.165
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.233
After features/support/hooks.rb:330 0.754
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
38.161
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.605
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the signing key used by the Upgrader is outdated 0.158
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 19.811
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.956
After features/support/hooks.rb:330 0.759
After features/support/hooks.rb:100 0.000