Project Number Date
test_Tails_ISO_stable 4999 05 Aug 2024, 20:07

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 74 2 11 0 0 87 5 2 7 19:3.037 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:32.581
Before features/support/hooks.rb:269 0.007
Given a computer 0.737
And I create a 7200 MiB disk named "old" 0.125
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 32.140
When I start Tails from USB drive "old" with network unplugged 1:53.863
Then the boot device has safe access rights 3.525
And Tails is running from USB drive "old" 0.410
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 7.272
After features/support/hooks.rb:100 0.012
Tags: @product
2:13.809
Before features/support/hooks.rb:269 0.007
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:25.967
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 34.761
And I take note of which tps features are available 2.411
Then a Tails persistence partition exists on USB drive "old" 0.963
And I shutdown Tails and wait for the computer to power off 9.142
After features/support/hooks.rb:326 0.244
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.582
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.745
Then Tails is running from USB drive "old" 0.383
And all tps features are active 2.068
When I write some files expected to persist 1.979
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
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.712
And I take note of which tps features are available 0.664
And I shutdown Tails and wait for the computer to power off 4.462
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.709
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.010
Tags: @product
3:16.457
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.241
And I log in to a new session 3:4.216
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:553:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:509: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/usb_upgrade.feature:62:in `And I log in to a new session'
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.000
And I plug USB drive "to_upgrade" 0.000
When I upgrade Tails to USB drive "to_upgrade" by cloning 0.000
Then the running Tails is installed on USB drive "to_upgrade" 0.000
And I unplug USB drive "to_upgrade" 0.000
And I unplug USB drive "__internal" 0.000
After features/support/hooks.rb:326 5.410 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:51:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4999/artifact/build-artifacts/01:51:06_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4999/artifact/build-artifacts/01:51:06_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4999/artifact/build-artifacts/01:51:06_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4999/artifact/build-artifacts/01:51:06_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
0.315
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.008
Steps
Given a computer 0.282
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 0.033
Call 
Call to virStorageVolLookupByName failed: Storage volume not found: no storage vol with matching name 'to_upgrade' (Libvirt::RetrieveError)
./features/support/helpers/storage_helper.rb:151:in `lookup_volume_by_name'
./features/support/helpers/storage_helper.rb:151:in `disk_path'
./features/support/helpers/vm_helper.rb:332:in `plug_drive'
./features/support/helpers/vm_helper.rb:411:in `set_disk_boot'
./features/step_definitions/common_steps.rb:144:in `/^the computer is set to boot from (.+?) drive "(.+?)"$/'
./features/step_definitions/common_steps.rb:276: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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
Hooks
After features/support/hooks.rb:326 4.298
Error message 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/hooks.rb:449:in `block (2 levels) in <top (required)>'
./features/support/hooks.rb:444:in `each'
./features/support/hooks.rb:444:in `After'
Output 1 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:51:11)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4999/artifact/build-artifacts/01:51:11_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4999/artifact/build-artifacts/01:51:11_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
7:21.864
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.113
And no SquashFS delta is installed 0.628
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.405
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.545
When the network is plugged 0.056
And Tor is ready 19.475
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.084
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.346
Given I shutdown Tails and wait for the computer to power off 9.116
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.379
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.401
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.268
When the network is plugged 0.042
And Tor is ready 46.758
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.655
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.678
Given I shutdown Tails and wait for the computer to power off 6.979
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.381
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.914
And the file system changes introduced in version 6.3~testoverlayfs are present 0.701
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.480
And Tor is ready 17.532
Then the Upgrader considers the system as up-to-date 0.352
# 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 15.419
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.187
After features/support/hooks.rb:326 0.809
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
39.426
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.847
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.859
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 22.194
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.950
After features/support/hooks.rb:326 1.846
After features/support/hooks.rb:100 0.000