Project Number Date
test_Tails_ISO_devel 3220 02 Jan 2024, 12:32

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 2 10 0 0 87 5 2 7 18:37.446 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:23.925
Before features/support/hooks.rb:245 0.025
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 17.796
When I start Tails from USB drive "old" with network unplugged 1:0.691
Then the boot device has safe access rights 3.179
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:291 3.542
After features/support/hooks.rb:75 0.013
Tags: @product
2:3.990
Before features/support/hooks.rb:245 0.010
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:7.990
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 45.707
And I take note of which tps features are available 1.677
Then a Tails persistence partition exists on USB drive "old" 0.916
And I shutdown Tails and wait for the computer to power off 7.087
After features/support/hooks.rb:291 0.182
After features/support/hooks.rb:75 0.014
Tags: @product
4:25.567
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:245 0.009
Steps
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:25.362
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:166:in `rescue in wait'
./features/support/helpers/screen.rb:159:in `wait'
./features/step_definitions/common_steps.rb:499:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:454: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/step_definitions/common_steps.rb:240: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:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:291 5.065 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:58:23)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3220/artifact/build-artifacts/01:58:23_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3220/artifact/build-artifacts/01:58:23_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3220/artifact/build-artifacts/01:58:23_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3220/artifact/build-artifacts/01:58:23_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:75 0.010
Tags: @product
2:35.811
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.921
And I log in to a new session 16.052
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.197
And I plug USB drive "to_upgrade" 2.496
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.037
Then the running Tails is installed on USB drive "to_upgrade" 12.691
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:291 6.680
After features/support/hooks.rb:75 0.000
Tags: @product
1:52.213
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:245 0.010
Steps
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.029
Then all tps features from the old Tails version are active 1.803
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.777
And the expected persistent files created with the old Tails version are present in the filesystem 0.053
Could 
Could not find expected file in persistent directory /home/amnesia/Persistent.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/helpers/misc_helpers.rb:21:in `assert_vmcommand_success'
./features/step_definitions/usb.rb:1025:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1024:in `each'
./features/step_definitions/usb.rb:1024:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:291 4.602 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:03:03)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3220/artifact/build-artifacts/02:03:03_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3220/artifact/build-artifacts/02:03:03_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3220/artifact/build-artifacts/02:03:03_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3220/artifact/build-artifacts/02:03:03_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
5:46.544
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.018
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.386
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.597
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.562
When the network is plugged 0.098
And Tor is ready 17.014
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.836
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.580
Given I shutdown Tails and wait for the computer to power off 6.409
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.929
Then Tails is running version 2.2~testoverlayfsng 0.126
And all tps features are active 2.510
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.462
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.307
When the network is plugged 0.034
And Tor is ready 17.114
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.736
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.202
Given I shutdown Tails and wait for the computer to power off 4.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.542
Then Tails is running version 2.3~testoverlayfsng 0.101
And all tps features are active 2.130
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.687
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.082
# 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.761
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.739
When the network is plugged 0.054
And Tor is ready 15.912
Then the Upgrader considers the system as up-to-date 0.268
# 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 26.138
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.354
After features/support/hooks.rb:291 0.725
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
29.393
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.372
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.566
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.076
And the signing key used by the Upgrader is outdated 0.637
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 14.790
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.915
After features/support/hooks.rb:291 0.811
After features/support/hooks.rb:75 0.000