Project Number Date
test_Tails_ISO_stable 5272 16 Nov 2024, 15:59

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 38:14.663 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:12.431
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.601
When I start Tails from USB drive "old" with network unplugged 1:35.399
Then the boot device has safe access rights 3.075
And Tails is running from USB drive "old" 0.392
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 3.747
After features/support/hooks.rb:100 0.011
Tags: @product
2:15.982
Before features/support/hooks.rb:269 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:30.176
Then Tails is running from USB drive "old" 0.402
And I create a persistent partition 34.057
And I take note of which tps features are available 1.530
Then a Tails persistence partition exists on USB drive "old" 0.863
And I shutdown Tails and wait for the computer to power off 8.774
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.011
Tags: @product
2:53.233
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.393
Then Tails is running from USB drive "old" 0.444
And all tps features are active 2.046
When I write some files expected to persist 2.016
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.348
And all persistence configuration files have safe access rights 0.702
And all persistent directories from the old Tails version have safe access rights 2.694
And I take note of which tps features are available 0.416
And I shutdown Tails and wait for the computer to power off 4.374
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.604
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.011
Tags: @product
2:33.133
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.132
And I log in to a new session 20.549
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.055
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.625
Then the running Tails is installed on USB drive "to_upgrade" 22.949
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:326 2.255
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.660
Before features/support/hooks.rb:269 0.006
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.756
Then all tps features from the old Tails version are active 1.568
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.228
And the expected persistent files created with the old Tails version are present in the filesystem 1.333
And all persistent directories from the old Tails version have safe access rights 2.219
After features/support/hooks.rb:326 0.634
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
25:32.006
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.664
And no SquashFS delta is installed 0.399
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.463
When the network is plugged 0.132
And Tor is ready 20.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.440
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.590
Given I shutdown Tails and wait for the computer to power off 8.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.482
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.180
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.232
When the network is plugged 0.097
And Tor is ready 17.287
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.463
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.371
Given I shutdown Tails and wait for the computer to power off 4.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:56.270
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:712:in `new'
./features/step_definitions/common_steps.rb:712:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298: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:326 10.852 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:07:40)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5272/artifact/build-artifacts/02:07:40_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5272/artifact/build-artifacts/02:07:40_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5272/artifact/build-artifacts/02:07:40_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.215
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.394
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.136
And the signing key used by the Upgrader is outdated 0.769
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 19.355
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.353
After features/support/hooks.rb:326 0.682
After features/support/hooks.rb:100 0.000