Project Number Date
test_Tails_ISO_stable 5383 09 Jan 2025, 12:59

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:55.322 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:0.377
Before features/support/hooks.rb:269 0.005
Given a computer 0.590
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.529
When I start Tails from USB drive "old" with network unplugged 1:25.295
Then the boot device has safe access rights 2.877
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 3.539
After features/support/hooks.rb:100 0.036
Tags: @product
2:4.472
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:22.293
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 31.065
And I take note of which tps features are available 1.533
Then a Tails persistence partition exists on USB drive "old" 0.765
And I shutdown Tails and wait for the computer to power off 8.308
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.009
Tags: @product
22:4.073
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.003
Steps
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 22:3.896
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: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:326 10.839 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:53:46)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5383/artifact/build-artifacts/01:53:46_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_stable/5383/artifact/build-artifacts/01:53:46_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_stable/5383/artifact/build-artifacts/01:53:46_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:30.400
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.058
And I log in to a new session 22.080
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.553
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.734
Then the running Tails is installed on USB drive "to_upgrade" 20.119
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.396
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.828
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.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.718
Then all tps features from the old Tails version are active 1.957
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.589
And the expected persistent files created with the old Tails version are present in the filesystem 0.062
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:1094:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1093:in `each'
./features/step_definitions/usb.rb:1093: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.155 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:58:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5383/artifact/build-artifacts/01:58:50_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_stable/5383/artifact/build-artifacts/01:58:50_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5383/artifact/build-artifacts/01:58:50_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5383/artifact/build-artifacts/01:58:50_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:19.909
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 11.966
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.630
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.080
And Tor is ready 22.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.510
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.227
Given I shutdown Tails and wait for the computer to power off 8.389
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.860
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.135
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.556
# 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.346
When the network is plugged 0.068
And Tor is ready 19.856
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.268
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.517
Given I shutdown Tails and wait for the computer to power off 4.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.395
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.262
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.063
And Tor is ready 18.880
Then the Upgrader considers the system as up-to-date 0.399
# 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.047
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.010
After features/support/hooks.rb:326 0.692
After features/support/hooks.rb:100 0.048
Tags: @product @automatic_upgrade
35.260
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.010
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.072
And Tor is ready 18.225
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.406
After features/support/hooks.rb:326 1.142
After features/support/hooks.rb:100 0.000