Project Number Date
test_Tails_ISO_stable 4818 30 Apr 2024, 19:00

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 1 11 0 0 87 6 1 7 21:21.529 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:15.394
Before features/support/hooks.rb:259 0.009
Given a computer 0.802
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 33.691
When I start Tails from USB drive "old" with network unplugged 1:35.302
Then the boot device has safe access rights 3.438
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:305 3.568
After features/support/hooks.rb:89 0.009
Tags: @product
2:23.565
Before features/support/hooks.rb:259 0.015
Given a computer 0.281
And I start Tails from USB drive "old" with network unplugged and I login 1:36.002
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 35.776
And I take note of which tps features are available 1.800
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.545
After features/support/hooks.rb:305 0.171
After features/support/hooks.rb:89 0.010
Tags: @product
2:59.099
Before features/support/hooks.rb:259 0.005
Given a computer 0.292
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.488
Then Tails is running from USB drive "old" 0.412
And all tps features are active 3.003
When I write some files expected to persist 2.147
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.647
And I take note of which tps features are available 0.543
And I shutdown Tails and wait for the computer to power off 4.214
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.709
After features/support/hooks.rb:305 0.095
After features/support/hooks.rb:89 0.009
Tags: @product
2:32.056
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 11.017
And I log in to a new session 20.244
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.529
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.326
Then the running Tails is installed on USB drive "to_upgrade" 20.099
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:305 2.073
After features/support/hooks.rb:89 0.000
Tags: @product
2:25.413
Before features/support/hooks.rb:259 0.005
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.162
Then all tps features from the old Tails version are active 1.869
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.777
And the expected persistent files created with the old Tails version are present in the filesystem 1.560
And all persistent directories from the old Tails version have safe access rights 2.484
After features/support/hooks.rb:305 0.591
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
8:8.034
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.040
And no SquashFS delta is installed 0.282
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.051
And Tor is ready 21.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.496
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.334
Given I shutdown Tails and wait for the computer to power off 10.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.086
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.499
And the file system changes introduced in version 6.2~testoverlayfs are present 0.395
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.401
# 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.255
When the network is plugged 0.035
And Tor is ready 16.692
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.620
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.944
Given I shutdown Tails and wait for the computer to power off 4.237
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:20.267
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/common_steps.rb:558:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:514: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:292: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:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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.669 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:58:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:58:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:58:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:58:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:58:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:89 0.017
Tags: @product @automatic_upgrade
37.966
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.212
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.422
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.810
But a current signing key is available on our website 0.000
When the network is plugged 0.143
And Tor is ready 22.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.565
After features/support/hooks.rb:305 0.832
After features/support/hooks.rb:89 0.000