Project Number Date
test_Tails_ISO_stable 5374 07 Jan 2025, 16:52

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:42.980 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:17.281
Before features/support/hooks.rb:269 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 33.407
When I start Tails from USB drive "old" with network unplugged 1:38.529
Then the boot device has safe access rights 3.088
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.577
After features/support/hooks.rb:100 0.011
Tags: @product
2:4.980
Before features/support/hooks.rb:269 0.007
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:22.572
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 31.395
And I take note of which tps features are available 1.464
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 8.182
After features/support/hooks.rb:326 0.166
After features/support/hooks.rb:100 0.009
Tags: @product
22:8.277
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.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 22:8.089
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.834 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:52:24)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5374/artifact/build-artifacts/01:52:24_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/5374/artifact/build-artifacts/01:52:24_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/5374/artifact/build-artifacts/01:52:24_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.007
Tags: @product
2:30.857
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 9.990
And I log in to a new session 17.992
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.731
And I plug USB drive "to_upgrade" 2.450
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.291
Then the running Tails is installed on USB drive "to_upgrade" 23.975
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 1.729
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.749
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.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.164
Then all tps features from the old Tails version are active 1.537
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.475
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: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.336 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:57:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5374/artifact/build-artifacts/01:57:16_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/5374/artifact/build-artifacts/01:57:16_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5374/artifact/build-artifacts/01:57:16_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/5374/artifact/build-artifacts/01:57:16_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
6:57.338
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 28.802
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.531
When the network is plugged 0.063
And Tor is ready 26.970
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.649
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.442
Given I shutdown Tails and wait for the computer to power off 8.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.369
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.233
And the file system changes introduced in version 6.2~testoverlayfs are present 0.417
And only the 6.2~testoverlayfs SquashFS delta is installed 0.115
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.415
# 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.292
When the network is plugged 0.070
And Tor is ready 19.495
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.720
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.562
Given I shutdown Tails and wait for the computer to power off 4.663
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.087
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.918
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.533
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.073
And Tor is ready 19.981
Then the Upgrader considers the system as up-to-date 0.313
# 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 15.107
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.340
After features/support/hooks.rb:326 0.891
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.495
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 9.458
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 18.992
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.556
After features/support/hooks.rb:326 0.924
After features/support/hooks.rb:100 0.000