Project Number Date
test_Tails_ISO_stable 4670 16 Feb 2024, 19:42

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 83 1 3 0 0 87 6 1 7 15:11.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:23.366
Before features/support/hooks.rb:245 0.005
Given a computer 0.141
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 20.288
When I start Tails from USB drive "old" with network unplugged 57.898
Then the boot device has safe access rights 3.004
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:291 3.458
After features/support/hooks.rb:75 0.009
Tags: @product
1:56.964
Before features/support/hooks.rb:245 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:3.827
Then Tails is running from USB drive "old" 0.442
And I create a persistent partition 42.775
And I take note of which tps features are available 1.751
Then a Tails persistence partition exists on USB drive "old" 0.898
And I shutdown Tails and wait for the computer to power off 7.068
After features/support/hooks.rb:291 0.139
After features/support/hooks.rb:75 0.010
Tags: @product
2:17.270
Before features/support/hooks.rb:245 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.651
Then Tails is running from USB drive "old" 0.384
And all tps features are active 1.962
When I write some files expected to persist 2.162
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.544
And all persistent directories from the old Tails version have safe access rights 2.834
And I take note of which tps features are available 0.516
And I shutdown Tails and wait for the computer to power off 3.131
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.672
After features/support/hooks.rb:291 0.121
After features/support/hooks.rb:75 0.009
Tags: @product
56.939
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:245 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.852
And I log in to a new session 15.450
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.024
And I plug USB drive "to_upgrade" 2.493
When I upgrade Tails to USB drive "to_upgrade" by cloning 28.118
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "tails-installer" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:148:in `new'
./features/step_definitions/usb.rb:148:in `/^I start Tails Installer$/'
./features/step_definitions/usb.rb:187:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_upgrade.feature:65:in `When I upgrade Tails to USB drive "to_upgrade" by cloning'
Then the running Tails is installed on USB drive "to_upgrade" 0.000
And I unplug USB drive "to_upgrade" 0.000
And I unplug USB drive "__internal" 0.000
After features/support/hooks.rb:291 4.196 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:22:20)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4670/artifact/build-artifacts/01:22:20_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4670/artifact/build-artifacts/01:22:20_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4670/artifact/build-artifacts/01:22:20_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4670/artifact/build-artifacts/01:22:20_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.864
Before features/support/hooks.rb:245 0.005
Given a computer 0.138
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.898
Then all tps features from the old Tails version are active 1.391
And Tails is running from USB drive "to_upgrade" 0.385
And the boot device has safe access rights 3.987
And the expected persistent files created with the old Tails version are present in the filesystem 1.562
And all persistent directories from the old Tails version have safe access rights 2.499
After features/support/hooks.rb:291 0.712
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:7.856
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.220
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.405
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.050
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.372
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.686
When the network is plugged 0.026
And Tor is ready 45.216
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.598
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.066
Given I shutdown Tails and wait for the computer to power off 5.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.886
Then Tails is running version 2.2~testoverlayfsng 0.099
And all tps features are active 1.773
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.424
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.274
# 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.397
When the network is plugged 0.034
And Tor is ready 14.906
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.742
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.676
Given I shutdown Tails and wait for the computer to power off 3.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.103
Then Tails is running version 2.3~testoverlayfsng 0.102
And all tps features are active 1.800
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.527
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.084
# 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.314
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.325
When the network is plugged 0.037
And Tor is ready 16.274
Then the Upgrader considers the system as up-to-date 0.268
# 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 27.269
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.155
After features/support/hooks.rb:291 0.755
After features/support/hooks.rb:75 0.069
Tags: @product @automatic_upgrade
27.726
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.248
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.386
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.064
And the signing key used by the Upgrader is outdated 0.680
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 13.599
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.716
After features/support/hooks.rb:291 0.591
After features/support/hooks.rb:75 0.000