Project Number Date
test_Tails_ISO_stable 4584 21 Dec 2023, 16:10

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 16:7.987 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:29.570
Before features/support/hooks.rb:245 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.071
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 19.727
When I start Tails from USB drive "old" with network unplugged 1:4.245
Then the boot device has safe access rights 3.316
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:291 3.488
After features/support/hooks.rb:75 0.062
Tags: @product
3:49.731
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:245 0.005
Steps
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 3:49.546
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:166:in `rescue in wait'
./features/support/helpers/screen.rb:159:in `wait'
./features/step_definitions/common_steps.rb:499:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:454: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:240: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 4.060 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:41:44)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4584/artifact/build-artifacts/01:41:44_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4584/artifact/build-artifacts/01:41:44_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4584/artifact/build-artifacts/01:41:44_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4584/artifact/build-artifacts/01:41:44_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:75 0.009
Tags: @product
57.123
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:245 0.005
Steps
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 56.946
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:327:in `initialize'
./features/support/helpers/dogtail.rb:256:in `new'
./features/support/helpers/dogtail.rb:256:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:264:in `child'
./features/step_definitions/usb.rb:653:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:665:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:236: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.088 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:42:45)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4584/artifact/build-artifacts/01:42:45_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/4584/artifact/build-artifacts/01:42:45_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/4584/artifact/build-artifacts/01:42:45_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/4584/artifact/build-artifacts/01:42:45_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:75 0.009
Tags: @product
2:32.390
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 9.940
And I log in to a new session 14.946
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.877
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.520
Then the running Tails is installed on USB drive "to_upgrade" 12.287
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:291 0.801
After features/support/hooks.rb:75 0.000
Tags: @product
58.039
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:245 0.006
Steps
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 57.864
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:327:in `initialize'
./features/support/helpers/dogtail.rb:256:in `new'
./features/support/helpers/dogtail.rb:256:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:264:in `child'
./features/step_definitions/usb.rb:653:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:665:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:236: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 3.956 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:46:20)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4584/artifact/build-artifacts/01:46:20_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4584/artifact/build-artifacts/01:46:20_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/4584/artifact/build-artifacts/01:46:20_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/4584/artifact/build-artifacts/01:46:20_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:52.978
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.659
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.287
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.048
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.561
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.497
When the network is plugged 0.052
And Tor is ready 16.911
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.554
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.815
Given I shutdown Tails and wait for the computer to power off 6.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.340
Then Tails is running version 2.2~testoverlayfsng 0.089
And all tps features are active 2.338
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.363
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.282
When the network is plugged 0.099
And Tor is ready 15.978
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.584
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.841
Given I shutdown Tails and wait for the computer to power off 4.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.780
Then Tails is running version 2.3~testoverlayfsng 0.107
And all tps features are active 2.038
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.532
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.057
# 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.308
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.366
When the network is plugged 0.054
And Tor is ready 13.876
Then the Upgrader considers the system as up-to-date 0.245
# 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 28.848
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.381
After features/support/hooks.rb:291 0.884
After features/support/hooks.rb:75 0.016
Tags: @product @automatic_upgrade
28.154
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.359
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.314
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.078
And the signing key used by the Upgrader is outdated 0.667
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 16.107
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.595
After features/support/hooks.rb:291 0.785
After features/support/hooks.rb:75 0.000