Project Number Date
test_Tails_ISO_stable 4832 08 May 2024, 12:47

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 57 2 28 0 0 87 5 2 7 17:50.193 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:20.027
Before features/support/hooks.rb:259 0.007
Given a computer 0.281
And I create a 7200 MiB disk named "old" 0.083
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.611
When I start Tails from USB drive "old" with network unplugged 1:44.956
Then the boot device has safe access rights 2.942
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.239
After features/support/hooks.rb:305 6.961
After features/support/hooks.rb:89 0.008
Tags: @product
2:23.389
Before features/support/hooks.rb:259 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:36.142
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 35.472
And I take note of which tps features are available 2.037
Then a Tails persistence partition exists on USB drive "old" 0.828
And I shutdown Tails and wait for the computer to power off 8.349
After features/support/hooks.rb:305 0.137
After features/support/hooks.rb:89 0.010
Tags: @product
2:50.439
Before features/support/hooks.rb:259 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.965
Then Tails is running from USB drive "old" 0.376
And all tps features are active 2.034
When I write some files expected to persist 1.660
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 2.461
And I take note of which tps features are available 0.885
And I shutdown Tails and wait for the computer to power off 4.460
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.730
After features/support/hooks.rb:305 0.160
After features/support/hooks.rb:89 0.008
Tags: @product
2:26.470
Before features/support/hooks.rb:259 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 10.120
And I log in to a new session 17.479
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.461
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.133
Then the running Tails is installed on USB drive "to_upgrade" 18.304
And I unplug USB drive "to_upgrade" 0.333
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:305 3.781
After features/support/hooks.rb:89 0.000
Tags: @product
2:15.104
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:259 0.008
Steps
Given a computer 0.307
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.796
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./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: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:305 4.489 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:09:28)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:09:28_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:09:28_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/4832/artifact/build-artifacts/02:09:28_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/4832/artifact/build-artifacts/02:09:28_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
4:57.899
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:259 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.574
And no SquashFS delta is installed 0.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
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.340
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.501
When the network is plugged 0.048
And Tor is ready 20.563
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.954
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.407
Given I shutdown Tails and wait for the computer to power off 1:33.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.311
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./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:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:305 4.434 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:14:31)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:14:31_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:14:31_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:14:31_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:14:31_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
36.862
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.690
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.435
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 1.099
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 18.639
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.876
After features/support/hooks.rb:305 1.418
After features/support/hooks.rb:89 0.000