Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 76 05 Jan 2025, 21:08

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 18:53.164 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:25.761
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 32.076
When I start Tails from USB drive "old" with network unplugged 1:45.579
Then the boot device has safe access rights 5.347
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.605
After features/support/hooks.rb:326 8.327
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.523
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:27.570
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 31.966
And I take note of which tps features are available 1.477
Then a Tails persistence partition exists on USB drive "old" 0.753
And I shutdown Tails and wait for the computer to power off 9.190
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.015
Tags: @product
2:55.780
Before features/support/hooks.rb:269 0.010
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.890
Then Tails is running from USB drive "old" 0.395
And all tps features are active 2.232
When I write some files expected to persist 2.329
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.472
And all persistent directories from the old Tails version have safe access rights 3.073
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.121
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.344
After features/support/hooks.rb:326 0.106
After features/support/hooks.rb:100 0.009
Tags: @product
3:17.041
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 11.767
And I log in to a new session 3:5.274
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:559:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:515: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.349 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:48:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:08_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_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:08_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:08_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:08_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
0.236
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 0.027
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:337:in `plug_drive'
./features/support/helpers/vm_helper.rb:416: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:282: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.335
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:48:13)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:13_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:13_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:26.159
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 13.376
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.575
When the network is plugged 0.093
And Tor is ready 48.721
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.634
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.525
Given I shutdown Tails and wait for the computer to power off 11.564
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.593
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.521
And the file system changes introduced in version 6.2~testoverlayfs are present 0.369
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.412
# 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.484
When the network is plugged 0.088
And Tor is ready 17.605
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.602
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.113
Given I shutdown Tails and wait for the computer to power off 6.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.214
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.284
And the file system changes introduced in version 6.3~testoverlayfs are present 0.586
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.355
When the network is plugged 0.070
And Tor is ready 17.824
Then the Upgrader considers the system as up-to-date 10.799
# 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 14.840
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.147
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
36.661
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.627
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 18.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.370
After features/support/hooks.rb:326 0.728
After features/support/hooks.rb:100 0.000