Project Number Date
test_Tails_ISO_stable 4562 11 Dec 2023, 12:15

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:25.755 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:25.524
Before features/support/hooks.rb:245 0.004
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 18.887
When I start Tails from USB drive "old" with network unplugged 1:1.483
Then the boot device has safe access rights 2.960
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:291 3.733
After features/support/hooks.rb:75 0.010
Tags: @product
3:52.977
Scenario Creating a 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 3:52.800
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.193 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:39:31)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4562/artifact/build-artifacts/01:39:31_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4562/artifact/build-artifacts/01:39:31_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4562/artifact/build-artifacts/01:39:31_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4562/artifact/build-artifacts/01:39:31_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:75 0.008
Tags: @product
59.635
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.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.465
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.082 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:40:34)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4562/artifact/build-artifacts/01:40: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_stable/4562/artifact/build-artifacts/01:40:34_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/4562/artifact/build-artifacts/01:40:34_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/4562/artifact/build-artifacts/01:40:34_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:75 0.010
Tags: @product
2:32.813
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 10.173
And I log in to a new session 16.871
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.039
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.237
Then the running Tails is installed on USB drive "to_upgrade" 14.664
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:291 5.227
After features/support/hooks.rb:75 0.000
Tags: @product
1:0.872
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.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.691
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 4.111 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:44:18)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4562/artifact/build-artifacts/01:44:18_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4562/artifact/build-artifacts/01:44:18_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/4562/artifact/build-artifacts/01:44:18_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/4562/artifact/build-artifacts/01:44:18_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:4.925
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.297
And no SquashFS delta is installed 0.148
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.347
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.122
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.437
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.667
When the network is plugged 0.043
And Tor is ready 18.656
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.826
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.145
Given I shutdown Tails and wait for the computer to power off 6.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.871
Then Tails is running version 2.2~testoverlayfsng 0.156
And all tps features are active 5.010
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.453
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.407
When the network is plugged 0.240
And Tor is ready 18.560
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.740
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.077
Given I shutdown Tails and wait for the computer to power off 5.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.143
Then Tails is running version 2.3~testoverlayfsng 0.158
And all tps features are active 2.478
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.627
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.094
# 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.297
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.411
When the network is plugged 0.036
And Tor is ready 18.672
Then the Upgrader considers the system as up-to-date 0.289
# 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 26.681
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.748
After features/support/hooks.rb:291 0.773
After features/support/hooks.rb:75 0.037
Tags: @product @automatic_upgrade
29.006
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.052
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.349
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the signing key used by the Upgrader is outdated 0.698
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 16.139
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.661
After features/support/hooks.rb:291 1.195
After features/support/hooks.rb:75 0.000