Project Number Date
test_Tails_ISO_stable 4836 09 May 2024, 17:17

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 38:30.777 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:21.466
Before features/support/hooks.rb:259 0.004
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.173
When I start Tails from USB drive "old" with network unplugged 1:44.859
Then the boot device has safe access rights 3.079
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.255
After features/support/hooks.rb:305 7.067
After features/support/hooks.rb:89 0.009
Tags: @product
2:19.257
Before features/support/hooks.rb:259 0.006
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:32.254
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 35.868
And I take note of which tps features are available 1.604
Then a Tails persistence partition exists on USB drive "old" 0.797
And I shutdown Tails and wait for the computer to power off 8.232
After features/support/hooks.rb:305 0.193
After features/support/hooks.rb:89 0.008
Tags: @product
22:4.535
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:259 0.006
Steps
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 22:4.332
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:295: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:305 9.850 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:03:46)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4836/artifact/build-artifacts/02:03:46_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_stable/4836/artifact/build-artifacts/02:03:46_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
After features/support/hooks.rb:89 0.009
Tags: @product
2:23.994
Before features/support/hooks.rb:259 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 11.416
And I log in to a new session 17.392
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.704
And I plug USB drive "to_upgrade" 2.474
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.734
Then the running Tails is installed on USB drive "to_upgrade" 16.862
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:305 6.786
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.032
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:259 0.006
Steps
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.366
Then all tps features from the old Tails version are active 1.758
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.308
And the expected persistent files created with the old Tails version are present in the filesystem 0.064
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:22:in `assert_vmcommand_success'
./features/step_definitions/usb.rb:1045:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1044:in `each'
./features/step_definitions/usb.rb:1044: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:305 4.439 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:08:45)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4836/artifact/build-artifacts/02:08:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4836/artifact/build-artifacts/02:08:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4836/artifact/build-artifacts/02:08:45_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_stable/4836/artifact/build-artifacts/02:08:45_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
6:26.777
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.053
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.458
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.046
And Tor is ready 17.211
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.173
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.347
Given I shutdown Tails and wait for the computer to power off 8.525
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.715
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.319
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.277
When the network is plugged 0.035
And Tor is ready 20.530
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.871
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.548
Given I shutdown Tails and wait for the computer to power off 6.757
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.798
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.518
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.394
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.359
And Tor is ready 16.474
Then the Upgrader considers the system as up-to-date 0.335
# 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.665
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.932
After features/support/hooks.rb:305 0.732
After features/support/hooks.rb:89 0.019
Tags: @product @automatic_upgrade
36.713
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.861
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.752
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.486
But a current signing key is available on our website 0.000
When the network is plugged 0.427
And Tor is ready 15.488
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.629
After features/support/hooks.rb:305 1.899
After features/support/hooks.rb:89 0.000