Project Number Date
test_Tails_ISO_20263-test-suite-without-spice 10 17 Mar 2025, 02:26

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 85 1 1 0 0 87 6 1 7 19:40.667 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:56.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 29.821
When I start Tails from USB drive "old" with network unplugged 1:20.937
Then the boot device has safe access rights 3.396
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:330 3.563
After features/support/hooks.rb:100 0.009
Tags: @product
1:58.539
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:20.491
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 29.237
And I take note of which tps features are available 1.237
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 6.337
After features/support/hooks.rb:330 0.124
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.807
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.833
Then Tails is running from USB drive "old" 0.366
And all tps features are active 1.798
When I write some files expected to persist 1.806
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.292
And all persistence configuration files have safe access rights 0.482
And all persistent directories from the old Tails version have safe access rights 2.280
And I take note of which tps features are available 0.438
And I shutdown Tails and wait for the computer to power off 4.343
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.980
After features/support/hooks.rb:330 0.121
After features/support/hooks.rb:100 0.017
Tags: @product
2:29.282
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.794
And I log in to a new session 20.093
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.508
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.132
Then the running Tails is installed on USB drive "to_upgrade" 18.883
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:330 2.116
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.431
Then all tps features from the old Tails version are active 1.681
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.132
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.713
After features/support/hooks.rb:330 1.988
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:21.250
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.886
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.060
And Tor is ready 18.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.186
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.449
Given I shutdown Tails and wait for the computer to power off 8.877
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.753
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.946
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.234
# 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.257
When the network is plugged 0.078
And Tor is ready 18.121
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.426
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.666
Given I shutdown Tails and wait for the computer to power off 4.353
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.652
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.881
And the file system changes introduced in version 6.3~testoverlayfs are present 0.517
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.054
And Tor is ready 25.633
Then the Upgrader considers the system as up-to-date 0.292
# 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 1:14.564
cannot 
cannot find UnsafeBrowserStartPage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/unsafe_browser.rb:63:in `/^the Unsafe Browser shows a warning as its start page$/'
./features/step_definitions/unsafe_browser.rb:71:in `/^the Unsafe Browser has started$/'
./features/step_definitions/browser.rb:70:in `/^I successfully start the Unsafe Browser(?: in "([^"]+)")?$/'
features/usb_upgrade.feature:122:in `And I successfully start the Unsafe Browser'
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:330 5.623 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:42:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/10/artifact/build-artifacts/01:42:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/10/artifact/build-artifacts/01:42:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/10/artifact/build-artifacts/01:42:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/10/artifact/build-artifacts/01:42:00_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
57.493
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.815
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 46.612
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.571
After features/support/hooks.rb:330 0.911
After features/support/hooks.rb:100 0.000