Project Number Date
test_Tails_ISO_devel 3519 24 Sep 2024, 12:26

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 19:53.875 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:1.719
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.713
When I start Tails from USB drive "old" with network unplugged 1:27.693
Then the boot device has safe access rights 3.042
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.571
After features/support/hooks.rb:100 0.007
Tags: @product
2:0.802
Before features/support/hooks.rb:269 0.004
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:21.118
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 30.639
And I take note of which tps features are available 1.427
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 6.245
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.009
Tags: @product
4:29.828
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:29.634
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:562:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:518: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:298: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:326 4.937 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:44:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3519/artifact/build-artifacts/01:44:00_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3519/artifact/build-artifacts/01:44:00_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/3519/artifact/build-artifacts/01:44:00_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3519/artifact/build-artifacts/01:44:00_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.031
Tags: @product
2:28.343
Before features/support/hooks.rb:269 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.136
And I log in to a new session 20.211
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.514
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.148
Then the running Tails is installed on USB drive "to_upgrade" 16.495
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 4.477
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.782
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.354
Then all tps features from the old Tails version are active 1.879
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 2.949
And the expected persistent files created with the old Tails version are present in the filesystem 0.047
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:1082:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1081:in `each'
./features/step_definitions/usb.rb:1081: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:326 5.437 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:48:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3519/artifact/build-artifacts/01:48:46_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3519/artifact/build-artifacts/01:48:46_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3519/artifact/build-artifacts/01:48:46_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3519/artifact/build-artifacts/01:48:46_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:8.327
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 11.715
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.467
When the network is plugged 0.079
And Tor is ready 19.188
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.424
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.340
Given I shutdown Tails and wait for the computer to power off 8.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.249
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.160
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.370
# 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.313
When the network is plugged 0.080
And Tor is ready 19.074
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.807
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.433
Given I shutdown Tails and wait for the computer to power off 4.295
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.912
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.108
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.086
And Tor is ready 17.069
Then the Upgrader considers the system as up-to-date 10.838
# 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 13.732
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.865
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.071
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 10.330
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.987
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 18.090
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.221
After features/support/hooks.rb:326 1.479
After features/support/hooks.rb:100 0.000