Project Number Date
test_Tails_ISO_5501-plaintext-locale-greeter 51 08 Jul 2025, 04:20

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 64 2 21 0 0 87 5 2 7 32:12.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
4:13.813
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.092
And I write an old version of the Tails USB image to disk "old" 59.333
When I start Tails from USB drive "old" with network unplugged 3:13.114
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:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 8.659 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 03:05:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:05:06_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:05:06_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:05:06_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:05:06_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.323
Tags: @product
4:15.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.362
Given a computer 1.392
And I start Tails from USB drive "old" with network unplugged and I login 2:51.513
Then Tails is running from USB drive "old" 0.897
And I create a persistent partition 1:1.562
And I take note of which tps features are available 5.560
Then a Tails persistence partition exists on USB drive "old" 5.597
And I shutdown Tails and wait for the computer to power off 8.995
After features/support/hooks.rb:330 0.224
After features/support/hooks.rb:100 0.008
Tags: @product
6:15.298
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:55.118
Then Tails is running from USB drive "old" 0.859
And all tps features are active 3.122
When I write some files expected to persist 9.843
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 2.165
And all persistence configuration files have safe access rights 1.582
And all persistent directories from the old Tails version have safe access rights 2.799
And I take note of which tps features are available 0.683
And I shutdown Tails and wait for the computer to power off 13.820
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 45.120
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.011
Tags: @product
4:24.357
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.778
And I log in to a new session 39.786
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.978
And I plug USB drive "to_upgrade" 10.498
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:19.395
Then the running Tails is installed on USB drive "to_upgrade" 49.476
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 6.302
After features/support/hooks.rb:100 0.000
Tags: @product
4:12.335
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.041
Given a computer 0.767
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:49.359
Then all tps features from the old Tails version are active 2.765
And Tails is running from USB drive "to_upgrade" 0.510
And the boot device has safe access rights 13.500
And the expected persistent files created with the old Tails version are present in the filesystem 1.706
And all persistent directories from the old Tails version have safe access rights 3.725
After features/support/hooks.rb:330 1.077
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:32.874
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:29.600
And no SquashFS delta is installed 0.691
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.113
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.647
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.536
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.559
When the network is plugged 0.085
And Tor is ready 41.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.126
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 31.436
Given I shutdown Tails and wait for the computer to power off 15.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:6.386
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.076
And the file system changes introduced in version 6.2~testoverlayfs are present 0.526
And only the 6.2~testoverlayfs SquashFS delta is installed 0.134
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.444
# 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.570
When the network is plugged 0.115
And Tor is ready 14.198
try_for() 
try_for() timeout expired
Last ignored exception was: ExecutionFailedInVM: Command failed: /usr/local/lib/tor_variable get --type=conf DisableNetwork
error code: 1
stdout: Unable to connect to tor. Maybe it's running without a ControlPort?

stderr: SocketError: Cannot connect to Tor's control port
.
<false> is not true.
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/common_steps.rb:629:in `block in check_disable_network'
./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:628:in `check_disable_network'
./features/step_definitions/common_steps.rb:656:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:620: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:628:in `check_disable_network'
./features/step_definitions/common_steps.rb:656:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:620:in `/^Tor is ready$/'
features/usb_upgrade.feature:105:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 5.598 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:32:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:32:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:32:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:32:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_5501-plaintext-locale-greeter/51/artifact/build-artifacts/03:32:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
1:18.124
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.951
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.474
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 56.583
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.827
After features/support/hooks.rb:330 1.158
After features/support/hooks.rb:100 0.000