Project Number Date
test_Tails_ISO_stable 5590 23 Apr 2025, 20:33

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 18:56.584 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:14.806
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 31.159
When I start Tails from USB drive "old" with network unplugged 1:36.704
Then the boot device has safe access rights 4.562
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 7.102
After features/support/hooks.rb:100 0.019
Tags: @product
2:10.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.311
And I start Tails from USB drive "old" with network unplugged and I login 1:26.677
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 30.873
And I take note of which tps features are available 2.598
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 8.837
After features/support/hooks.rb:330 0.186
After features/support/hooks.rb:100 0.011
Tags: @product
1:38.239
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.007
Steps
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.001
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:460: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:459: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:459: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:330 4.898 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:44:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5590/artifact/build-artifacts/01:44:25_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_stable/5590/artifact/build-artifacts/01:44: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_stable/5590/artifact/build-artifacts/01:44: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_stable/5590/artifact/build-artifacts/01:44:25_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:43.802
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.222
And I log in to a new session 20.929
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.670
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.228
Then the running Tails is installed on USB drive "to_upgrade" 28.933
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 1.850
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.900
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.004
Steps
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.196
Then all tps features from the old Tails version are active 1.785
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.330
And the expected persistent files created with the old Tails version are present in the filesystem 0.056
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.490 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:49:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5590/artifact/build-artifacts/01:49:47_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/5590/artifact/build-artifacts/01:49:47_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5590/artifact/build-artifacts/01:49:47_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/5590/artifact/build-artifacts/01:49:47_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:59.220
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.363
And no SquashFS delta is installed 0.145
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.404
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.663
When the network is plugged 0.072
And Tor is ready 50.191
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.600
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.887
Given I shutdown Tails and wait for the computer to power off 10.734
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.724
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.143
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.136
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.403
# 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.391
When the network is plugged 0.065
And Tor is ready 20.004
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.748
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.791
Given I shutdown Tails and wait for the computer to power off 4.325
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.082
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.057
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.064
And Tor is ready 21.121
Then the Upgrader considers the system as up-to-date 0.354
# 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.933
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.788
After features/support/hooks.rb:330 0.743
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.604
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 19.885
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.987
After features/support/hooks.rb:330 1.045
After features/support/hooks.rb:100 0.000