Project Number Date
test_Tails_ISO_stable 5106 20 Sep 2024, 12:37

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 37:42.079 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:3.062
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.340
When I start Tails from USB drive "old" with network unplugged 1:27.540
Then the boot device has safe access rights 2.918
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 7.098
After features/support/hooks.rb:100 0.009
Tags: @product
2:0.696
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:19.152
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 30.257
And I take note of which tps features are available 1.380
Then a Tails persistence partition exists on USB drive "old" 0.811
And I shutdown Tails and wait for the computer to power off 8.600
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.009
Tags: @product
22:2.354
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.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 22:2.173
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:715:in `new'
./features/step_definitions/common_steps.rb:715:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:301: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 10.815 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:54:52)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5106/artifact/build-artifacts/01:54:52_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/5106/artifact/build-artifacts/01:54:52_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_stable/5106/artifact/build-artifacts/01:54:52_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.862
Before features/support/hooks.rb:269 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 10.953
And I log in to a new session 17.726
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.549
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.827
Then the running Tails is installed on USB drive "to_upgrade" 17.006
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.021
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.226
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.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.875
Then all tps features from the old Tails version are active 1.554
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.125
And the expected persistent files created with the old Tails version are present in the filesystem 0.078
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.404 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:59:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5106/artifact/build-artifacts/01:59:33_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_stable/5106/artifact/build-artifacts/01:59:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5106/artifact/build-artifacts/01:59:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5106/artifact/build-artifacts/01:59:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:30.111
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 11.907
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
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.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.081
And Tor is ready 17.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.941
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.274
Given I shutdown Tails and wait for the computer to power off 10.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.180
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.094
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.249
When the network is plugged 0.058
And Tor is ready 17.374
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.571
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.873
Given I shutdown Tails and wait for the computer to power off 4.585
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.386
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.066
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.108
And Tor is ready 20.584
Then the Upgrader considers the system as up-to-date 0.298
# 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.869
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.020
After features/support/hooks.rb:326 0.746
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.764
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 9.757
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 1.960
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.289
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.281
After features/support/hooks.rb:326 0.659
After features/support/hooks.rb:100 0.000