Project Number Date
test_Tails_ISO_stable 4819 01 May 2024, 12:35

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:53.496 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:58.928
Before features/support/hooks.rb:259 0.007
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 31.463
When I start Tails from USB drive "old" with network unplugged 1:22.159
Then the boot device has safe access rights 3.014
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:305 6.865
After features/support/hooks.rb:89 0.010
Tags: @product
2:9.069
Before features/support/hooks.rb:259 0.009
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:22.915
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 34.184
And I take note of which tps features are available 1.617
Then a Tails persistence partition exists on USB drive "old" 0.882
And I shutdown Tails and wait for the computer to power off 8.906
After features/support/hooks.rb:305 0.188
After features/support/hooks.rb:89 0.009
Tags: @product
22:3.961
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.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 22:3.771
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.882 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:59:44)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4819/artifact/build-artifacts/01:59:44_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/4819/artifact/build-artifacts/01:59:44_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
After features/support/hooks.rb:89 0.020
Tags: @product
2:30.401
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.139
And I log in to a new session 19.886
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.664
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.546
Then the running Tails is installed on USB drive "to_upgrade" 20.329
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:305 3.864
After features/support/hooks.rb:89 0.000
Tags: @product
2:8.645
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:2.891
Then all tps features from the old Tails version are active 1.553
And Tails is running from USB drive "to_upgrade" 0.376
And the boot device has safe access rights 3.574
And the expected persistent files created with the old Tails version are present in the filesystem 0.059
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.334 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:04:37)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4819/artifact/build-artifacts/02:04:37_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4819/artifact/build-artifacts/02:04:37_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/4819/artifact/build-artifacts/02:04:37_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/4819/artifact/build-artifacts/02:04:37_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
6:25.659
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.842
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.044
And Tor is ready 23.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.796
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.731
Given I shutdown Tails and wait for the computer to power off 8.768
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.448
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.179
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.248
When the network is plugged 0.027
And Tor is ready 20.329
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.626
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.015
Given I shutdown Tails and wait for the computer to power off 4.680
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.244
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.142
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.042
And Tor is ready 19.109
Then the Upgrader considers the system as up-to-date 0.412
# 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.637
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.083
After features/support/hooks.rb:305 0.656
After features/support/hooks.rb:89 0.023
Tags: @product @automatic_upgrade
36.831
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.932
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.488
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 19.476
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.568
After features/support/hooks.rb:305 0.640
After features/support/hooks.rb:89 0.000