Project Number Date
test_Tails_ISO_20448-tor-browser-14-force-all-tests 30 30 Aug 2024, 07:32

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 18:34.241 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.127
Before features/support/hooks.rb:269 0.007
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.627
When I start Tails from USB drive "old" with network unplugged 1:32.138
Then the boot device has safe access rights 3.008
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.294
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:326 0.929
After features/support/hooks.rb:100 0.010
Tags: @product
4:10.627
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.007
Steps
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 4:10.422
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/common_steps.rb:562:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:518: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:298: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.986 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:45:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:45:15_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_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:45:15_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:45:15_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:45:15_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.010
Tags: @product
1:13.139
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.007
Steps
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.935
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:668:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:680:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:294: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 5.024 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:46:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:46:34_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_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:46:34_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_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:46:34_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_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:46:34_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:37.570
Before features/support/hooks.rb:269 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 13.238
And I log in to a new session 23.549
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.409
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.572
Then the running Tails is installed on USB drive "to_upgrade" 20.991
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:326 1.779
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.419
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.203
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:668:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:680:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:294: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 5.154 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:50:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:50:37_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_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:50:37_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:50:37_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20448-tor-browser-14-force-all-tests/30/artifact/build-artifacts/01:50:37_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:28.174
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 13.795
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.076
And Tor is ready 22.077
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.532
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.813
Given I shutdown Tails and wait for the computer to power off 15.330
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.606
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.158
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.293
When the network is plugged 0.082
And Tor is ready 16.981
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.226
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.160
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.036
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.069
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.099
And Tor is ready 17.514
Then the Upgrader considers the system as up-to-date 0.323
# 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 15.463
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.009
After features/support/hooks.rb:326 1.015
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
38.181
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 9.796
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.443
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.964
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 20.230
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.598
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.000