Project Number Date
test_Tails_ISO_stable 5068 04 Sep 2024, 13:39

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 39:1.786 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:21.267
Before features/support/hooks.rb:269 0.005
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.255
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 30.066
When I start Tails from USB drive "old" with network unplugged 1:45.446
Then the boot device has safe access rights 3.222
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.648
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.781
Before features/support/hooks.rb:269 0.005
Given a computer 0.449
And I start Tails from USB drive "old" with network unplugged and I login 1:28.224
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 29.852
And I take note of which tps features are available 1.683
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.406
After features/support/hooks.rb:326 0.263
After features/support/hooks.rb:100 0.007
Tags: @product
3:4.654
Before features/support/hooks.rb:269 0.004
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.035
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.263
When I write some files expected to persist 1.769
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.474
And all persistent directories from the old Tails version have safe access rights 2.687
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 4.365
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.805
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.121
Before features/support/hooks.rb:269 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.970
And I log in to a new session 20.246
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.526
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.948
Then the running Tails is installed on USB drive "to_upgrade" 19.532
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 3.003
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.335
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.111
Then all tps features from the old Tails version are active 1.507
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.091
And the expected persistent files created with the old Tails version are present in the filesystem 1.536
And all persistent directories from the old Tails version have safe access rights 2.553
After features/support/hooks.rb:326 0.805
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
26:0.208
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.234
And no SquashFS delta is installed 0.414
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.719
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.388
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.523
When the network is plugged 0.182
And Tor is ready 20.234
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.772
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.830
Given I shutdown Tails and wait for the computer to power off 13.154
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.862
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.252
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.273
When the network is plugged 0.069
And Tor is ready 19.407
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.233
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.203
Given I shutdown Tails and wait for the computer to power off 4.521
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:54.122
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:715:in `new'
./features/step_definitions/common_steps.rb:715:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:301: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.990 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:11:28)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5068/artifact/build-artifacts/02:11:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5068/artifact/build-artifacts/02:11:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5068/artifact/build-artifacts/02:11:28_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.416
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.264
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.063
And the signing key used by the Upgrader is outdated 0.873
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 19.850
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.930
After features/support/hooks.rb:326 0.815
After features/support/hooks.rb:100 0.000