Project Number Date
test_Tails_ISO_devel 3694 16 Feb 2025, 12:47

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 19:33.464 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:15.202
Before features/support/hooks.rb:269 0.005
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.079
And I write an old version of the Tails USB image to disk "old" 31.648
When I start Tails from USB drive "old" with network unplugged 1:37.921
Then the boot device has safe access rights 3.162
And Tails is running from USB drive "old" 0.437
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 3.498
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.775
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:25.323
Then Tails is running from USB drive "old" 0.418
And I create a persistent partition 31.806
And I take note of which tps features are available 1.873
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.337
After features/support/hooks.rb:326 0.211
After features/support/hooks.rb:100 0.007
Tags: @product
1:35.092
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:34.890
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:451:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:450:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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 4.899 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:40:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3694/artifact/build-artifacts/01:40:35_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3694/artifact/build-artifacts/01:40:35_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/3694/artifact/build-artifacts/01:40:35_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/3694/artifact/build-artifacts/01:40:35_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.272
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.026
And I log in to a new session 18.193
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.755
And I plug USB drive "to_upgrade" 2.363
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.525
Then the running Tails is installed on USB drive "to_upgrade" 20.972
And I unplug USB drive "to_upgrade" 0.236
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:326 6.901
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.434
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.926
Then all tps features from the old Tails version are active 1.656
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.247
And the expected persistent files created with the old Tails version are present in the filesystem 0.055
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:326 5.475 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:45:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3694/artifact/build-artifacts/01:45:45_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/3694/artifact/build-artifacts/01:45:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3694/artifact/build-artifacts/01:45:45_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/3694/artifact/build-artifacts/01:45:45_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
7:56.250
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 14.732
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.460
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.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.067
And Tor is ready 26.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.786
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.260
Given I shutdown Tails and wait for the computer to power off 1:19.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.041
Then Tails is running version 6.2~testoverlayfs 0.030
And all tps features are active 2.294
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.343
# 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.302
When the network is plugged 0.064
And Tor is ready 18.866
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.747
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.155
Given I shutdown Tails and wait for the computer to power off 4.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.896
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.471
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.387
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.400
When the network is plugged 0.063
And Tor is ready 17.112
Then the Upgrader considers the system as up-to-date 0.327
# 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 16.287
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.917
After features/support/hooks.rb:326 0.747
After features/support/hooks.rb:100 0.062
Tags: @product @automatic_upgrade
40.436
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.338
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.577
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 23.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.281
After features/support/hooks.rb:326 1.041
After features/support/hooks.rb:100 0.000