Project Number Date
test_Tails_ISO_stable 4723 18 Mar 2024, 12:10

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 40 4 43 0 0 87 3 4 7 12:43.953 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
1:48.318
Before features/support/hooks.rb:245 0.005
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 20.701
When I start Tails from USB drive "old" with network unplugged 1:21.649
Then the boot device has safe access rights 3.676
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:291 3.756
After features/support/hooks.rb:75 0.045
Tags: @product
1:32.576
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:245 0.006
Steps
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 1:32.331
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:450: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:449:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:288: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:449:in `/^the computer (?:re)?boots Tails( with genuine APT sources)?$/'
./features/step_definitions/common_steps.rb:288: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:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:291 3.979 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:32:36)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:32:36_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:32:36_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:32:36_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:32:36_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:75 0.011
Tags: @product
1:7.742
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:245 0.006
Steps
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.557
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/usb.rb:642:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:654:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:290: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:291 4.140 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:33:48)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:33:48_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/4723/artifact/build-artifacts/01:33:48_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:33:48_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:33:48_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:75 0.008
Tags: @product
2:35.292
Before features/support/hooks.rb:245 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 11.702
And I log in to a new session 18.833
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.448
And I plug USB drive "to_upgrade" 2.490
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.031
Then the running Tails is installed on USB drive "to_upgrade" 14.361
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:291 3.693
After features/support/hooks.rb:75 0.000
Tags: @product
1:13.434
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:245 0.007
Steps
Given a computer 0.232
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.201
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/usb.rb:642:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:654:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:290: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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:291 4.479 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:37:45)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:37:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:37:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:37:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:37:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
3:53.530
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:245 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.021
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.584
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.054
And Tor is ready 21.258
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.952
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.665
Given I shutdown Tails and wait for the computer to power off 3:0.044
try_for() 
try_for() timeout expired (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:838:in `/^Tails eventually (shuts down|restarts)$/'
./features/step_definitions/common_steps.rb:850:in `/^I shutdown Tails and wait for the computer to power off$/'
features/usb_upgrade.feature:92:in `Given I shutdown Tails and wait for the computer to power off'
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.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
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:291 9.590 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:41:43)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:41:43_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4723/artifact/build-artifacts/01:41:43_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
After features/support/hooks.rb:75 0.000
Tags: @product @automatic_upgrade
33.057
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.450
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.537
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 15.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.673
After features/support/hooks.rb:291 1.023
After features/support/hooks.rb:75 0.000