Project Number Date
test_Tails_ISO_feature-arti 13 28 Nov 2024, 16:37

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 58 4 25 0 0 87 3 4 7 15:41.013 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:7.286
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.946
When I start Tails from USB drive "old" with network unplugged 1:34.069
FileNotFoundError: 
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./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:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:711:in `block in file_append'
./features/support/helpers/vm_helper.rb:604:in `file_open'
./features/support/helpers/vm_helper.rb:711:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:467:in `/^the computer (?:re)?boots Tails$/'
./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: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:326 4.823 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:26:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/13/artifact/build-artifacts/02:26:34_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_feature-arti/13/artifact/build-artifacts/02:26:34_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/13/artifact/build-artifacts/02:26:34_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/13/artifact/build-artifacts/02:26:34_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.007
Tags: @product
1:4.243
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:4.043
FileNotFoundError: 
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./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:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:711:in `block in file_append'
./features/support/helpers/vm_helper.rb:604:in `file_open'
./features/support/helpers/vm_helper.rb:711:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:467:in `/^the computer (?:re)?boots Tails$/'
./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:326 4.809 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:27:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/13/artifact/build-artifacts/02:27:43_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_feature-arti/13/artifact/build-artifacts/02:27:43_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/13/artifact/build-artifacts/02:27:43_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/13/artifact/build-artifacts/02:27:43_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Tags: @product
1:0.839
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.602
FileNotFoundError: 
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./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:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:711:in `block in file_append'
./features/support/helpers/vm_helper.rb:604:in `file_open'
./features/support/helpers/vm_helper.rb:711:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:467:in `/^the computer (?:re)?boots Tails$/'
./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: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 4.858 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:28:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/13/artifact/build-artifacts/02:28:48_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_feature-arti/13/artifact/build-artifacts/02:28: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_feature-arti/13/artifact/build-artifacts/02:28:48_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_feature-arti/13/artifact/build-artifacts/02:28:48_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:35.226
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 11.436
And I log in to a new session 19.991
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.654
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.130
Then the running Tails is installed on USB drive "to_upgrade" 25.164
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 6.940
After features/support/hooks.rb:100 0.000
Tags: @product
1:25.595
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.007
Steps
Given a computer 0.249
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:25.346
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:668:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:700:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:302: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:326 4.984 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:33:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/13/artifact/build-artifacts/02:33:01_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_feature-arti/13/artifact/build-artifacts/02:33:01_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/13/artifact/build-artifacts/02:33:01_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/13/artifact/build-artifacts/02:33:01_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:26.850
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 12.109
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.477
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.072
And Tor is ready 23.868
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.790
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.764
Given I shutdown Tails and wait for the computer to power off 10.936
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.831
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.278
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
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.314
# 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.288
When the network is plugged 0.061
And Tor is ready 18.525
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.562
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.841
Given I shutdown Tails and wait for the computer to power off 4.268
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.182
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.925
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.069
And Tor is ready 16.486
Then the Upgrader considers the system as up-to-date 10.839
# 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.768
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.015
After features/support/hooks.rb:326 0.660
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
1:0.972
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.310
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.787
But a current signing key is available on our website 0.000
When the network is plugged 0.170
And Tor is ready 48.603
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.615
After features/support/hooks.rb:326 0.662
After features/support/hooks.rb:100 0.000