Project Number Date
test_Tails_ISO_devel 3737 13 Mar 2025, 12:53

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 65 3 19 0 0 87 4 3 7 19:54.418 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:31.704
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.289
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 52.056
When I start Tails from USB drive "old" with network unplugged 1:33.825
Then the boot device has safe access rights 3.365
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:330 3.490
After features/support/hooks.rb:100 0.008
Tags: @product
4:8.821
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 4:8.588
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:566:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:522:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:295: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:330 5.142 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:39:02)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3737/artifact/build-artifacts/01:39:02_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3737/artifact/build-artifacts/01:39:02_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3737/artifact/build-artifacts/01:39:02_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3737/artifact/build-artifacts/01:39:02_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.014
Tags: @product
1:15.475
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.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:15.258
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:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291: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 5.086 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:40:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3737/artifact/build-artifacts/01:40:23_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_devel/3737/artifact/build-artifacts/01:40:23_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_devel/3737/artifact/build-artifacts/01:40:23_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_devel/3737/artifact/build-artifacts/01:40:23_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.012
Tags: @product
2:32.785
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 without a persistent partition and stopped at Tails Greeter's login screen 12.488
And I log in to a new session 19.444
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.414
And I plug USB drive "to_upgrade" 2.524
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.293
Then the running Tails is installed on USB drive "to_upgrade" 21.172
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 1.741
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.131
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.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:27.923
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:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291: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:330 5.093 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:44:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3737/artifact/build-artifacts/01:44:31_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_devel/3737/artifact/build-artifacts/01:44:31_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3737/artifact/build-artifacts/01:44:31_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3737/artifact/build-artifacts/01:44:31_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
7:16.398
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 13.871
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.621
When the network is plugged 0.117
And Tor is ready 21.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.531
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.096
Given I shutdown Tails and wait for the computer to power off 11.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.512
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.544
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.283
When the network is plugged 0.090
And Tor is ready 20.115
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.463
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.736
Given I shutdown Tails and wait for the computer to power off 4.548
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.946
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.075
And Tor is ready 47.810
Then the Upgrader considers the system as up-to-date 0.319
# 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 1.108
After features/support/hooks.rb:330 0.767
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
41.101
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.955
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.002
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 21.986
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.877
After features/support/hooks.rb:330 0.884
After features/support/hooks.rb:100 0.000