Project Number Date
test_Tails_ISO_20263-test-suite-without-spice 20 27 Mar 2025, 03:19

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 20:11.707 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:49.881
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 28.336
When I start Tails from USB drive "old" with network unplugged 1:15.908
Then the boot device has safe access rights 3.409
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:330 7.149
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.967
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:22.995
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 30.904
And I take note of which tps features are available 1.411
Then a Tails persistence partition exists on USB drive "old" 0.849
And I shutdown Tails and wait for the computer to power off 8.295
After features/support/hooks.rb:330 0.116
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.011
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.537
Then Tails is running from USB drive "old" 0.803
And all tps features are active 2.182
When I write some files expected to persist 1.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.790
And all persistence configuration files have safe access rights 0.883
And all persistent directories from the old Tails version have safe access rights 2.830
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.324
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.122
After features/support/hooks.rb:330 0.112
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.423
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 without a persistent partition and stopped at Tails Greeter's login screen 9.532
And I log in to a new session 19.820
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.514
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.370
Then the running Tails is installed on USB drive "to_upgrade" 26.398
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 1.044
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.930
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.824
Then all tps features from the old Tails version are active 1.529
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 2.995
And the expected persistent files created with the old Tails version are present in the filesystem 1.491
And all persistent directories from the old Tails version have safe access rights 2.585
After features/support/hooks.rb:330 1.594
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:55.165
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.466
And no SquashFS delta is installed 0.411
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.686
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.700
When the network is plugged 0.083
And Tor is ready 48.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.589
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.271
Given I shutdown Tails and wait for the computer to power off 8.686
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.745
Then Tails is running version 6.2~testoverlayfs 0.033
And all tps features are active 2.056
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.268
# 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.254
When the network is plugged 0.082
And Tor is ready 18.489
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.709
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.736
Given I shutdown Tails and wait for the computer to power off 6.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.316
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.643
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.265
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.086
And Tor is ready 16.592
Then the Upgrader considers the system as up-to-date 0.304
# 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.256
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:78: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 7.191 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:16:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/02:16:45_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/20/artifact/build-artifacts/02:16:45_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/20/artifact/build-artifacts/02:16:45_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/20/artifact/build-artifacts/02:16:45_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.325
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.667
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.094
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 19.171
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.132
After features/support/hooks.rb:330 0.730
After features/support/hooks.rb:100 0.000