Project Number Date
test_Tails_ISO_stable 5443 05 Feb 2025, 16:51

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:51.306 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:9.569
Before features/support/hooks.rb:269 0.004
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 28.206
When I start Tails from USB drive "old" with network unplugged 1:35.893
Then the boot device has safe access rights 3.137
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 8.275
After features/support/hooks.rb:100 0.014
Tags: @product
2:4.271
Before features/support/hooks.rb:269 0.007
Given a computer 0.283
And I start Tails from USB drive "old" with network unplugged and I login 1:22.291
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 30.906
And I take note of which tps features are available 1.372
Then a Tails persistence partition exists on USB drive "old" 0.866
And I shutdown Tails and wait for the computer to power off 8.251
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.010
Tags: @product
21:59.698
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.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 21:59.466
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.817 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:57:37)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5443/artifact/build-artifacts/01:57:37_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/5443/artifact/build-artifacts/01:57:37_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/5443/artifact/build-artifacts/01:57:37_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.255
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 13.837
And I log in to a new session 20.836
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.571
And I plug USB drive "to_upgrade" 2.370
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.214
Then the running Tails is installed on USB drive "to_upgrade" 22.987
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.945
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.809
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.494
Then all tps features from the old Tails version are active 1.601
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.096
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: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.030 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:02:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5443/artifact/build-artifacts/02:02:38_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/5443/artifact/build-artifacts/02:02:38_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5443/artifact/build-artifacts/02:02:38_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/5443/artifact/build-artifacts/02:02:38_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:12.144
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 13.944
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.373
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.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.949
When the network is plugged 0.062
And Tor is ready 20.107
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.614
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.874
Given I shutdown Tails and wait for the computer to power off 8.567
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.964
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.112
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
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.329
# 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.240
When the network is plugged 0.089
And Tor is ready 20.007
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.456
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.132
Given I shutdown Tails and wait for the computer to power off 6.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.629
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.003
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.070
And Tor is ready 20.132
Then the Upgrader considers the system as up-to-date 0.305
# 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.923
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.944
After features/support/hooks.rb:326 0.717
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.558
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.680
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.860
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 20.130
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.660
After features/support/hooks.rb:326 0.646
After features/support/hooks.rb:100 0.000