Project Number Date
test_Tails_ISO_stable 4672 18 Feb 2024, 12:02

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 16:10.045 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:32.534
Before features/support/hooks.rb:245 0.006
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 18.789
When I start Tails from USB drive "old" with network unplugged 1:8.328
Then the boot device has safe access rights 3.127
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:291 3.492
After features/support/hooks.rb:75 0.009
Tags: @product
1:56.571
Before features/support/hooks.rb:245 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:3.028
Then Tails is running from USB drive "old" 0.422
And I create a persistent partition 43.550
And I take note of which tps features are available 1.393
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.076
After features/support/hooks.rb:291 0.170
After features/support/hooks.rb:75 0.009
Tags: @product
2:18.289
Before features/support/hooks.rb:245 0.006
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.304
Then Tails is running from USB drive "old" 0.364
And all tps features are active 2.182
When I write some files expected to persist 1.893
# 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.398
And all persistent directories from the old Tails version have safe access rights 2.901
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.211
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.193
After features/support/hooks.rb:291 0.106
After features/support/hooks.rb:75 0.009
Tags: @product
56.938
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:245 0.006
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.695
And I log in to a new session 15.699
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.006
And I plug USB drive "to_upgrade" 2.496
When I upgrade Tails to USB drive "to_upgrade" by cloning 28.040
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.312 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:24:18)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4672/artifact/build-artifacts/01:24:18_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4672/artifact/build-artifacts/01:24:18_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4672/artifact/build-artifacts/01:24:18_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/4672/artifact/build-artifacts/01:24:18_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.095
Before features/support/hooks.rb:245 0.006
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.723
Then all tps features from the old Tails version are active 1.772
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.634
And the expected persistent files created with the old Tails version are present in the filesystem 1.686
And all persistent directories from the old Tails version have safe access rights 2.776
After features/support/hooks.rb:291 0.920
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:33.287
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 11.134
And no SquashFS delta is installed 0.111
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.059
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.320
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.596
When the network is plugged 0.048
And Tor is ready 15.745
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.656
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.986
Given I shutdown Tails and wait for the computer to power off 6.353
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.488
Then Tails is running version 2.2~testoverlayfsng 0.122
And all tps features are active 2.413
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.494
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.290
When the network is plugged 0.033
And Tor is ready 14.453
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.699
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.900
Given I shutdown Tails and wait for the computer to power off 4.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.635
Then Tails is running version 2.3~testoverlayfsng 0.095
And all tps features are active 2.254
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.573
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.073
# 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.318
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.340
When the network is plugged 0.038
And Tor is ready 42.537
Then the Upgrader considers the system as up-to-date 0.252
# 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.145
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.058
After features/support/hooks.rb:291 0.845
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
53.328
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.971
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.315
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.086
And the signing key used by the Upgrader is outdated 0.631
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 41.647
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.637
After features/support/hooks.rb:291 1.341
After features/support/hooks.rb:75 0.000