Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 72 18 Dec 2024, 07:30

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 63 1 23 0 0 87 6 1 7 35:53.204 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:39.866
Before features/support/hooks.rb:269 0.005
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 1:2.267
When I start Tails from USB drive "old" with network unplugged 1:32.248
Then the boot device has safe access rights 2.976
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.512
After features/support/hooks.rb:100 0.068
Tags: @product
2:16.117
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:28.803
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 33.953
And I take note of which tps features are available 1.466
Then a Tails persistence partition exists on USB drive "old" 0.897
And I shutdown Tails and wait for the computer to power off 10.445
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.143
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.605
Then Tails is running from USB drive "old" 0.374
And all tps features are active 2.306
When I write some files expected to persist 1.734
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.594
And all persistent directories from the old Tails version have safe access rights 2.788
And I take note of which tps features are available 0.797
And I shutdown Tails and wait for the computer to power off 4.425
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.103
After features/support/hooks.rb:326 0.116
After features/support/hooks.rb:100 0.009
Tags: @product
2:24.075
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 9.954
And I log in to a new session 18.648
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.693
And I plug USB drive "to_upgrade" 2.775
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.991
Then the running Tails is installed on USB drive "to_upgrade" 17.566
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 3.549
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.945
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.378
Then all tps features from the old Tails version are active 1.879
And Tails is running from USB drive "to_upgrade" 0.569
And the boot device has safe access rights 3.092
And the expected persistent files created with the old Tails version are present in the filesystem 1.352
And all persistent directories from the old Tails version have safe access rights 2.480
After features/support/hooks.rb:326 1.188
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
22:53.245
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.849
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.061
And Tor is ready 22.281
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.635
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.691
Given I shutdown Tails and wait for the computer to power off 10.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:50.507
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:712:in `new'
./features/step_definitions/common_steps.rb:712:in `/^all notifications have disappeared$/'
./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:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:326 10.797 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:06:08)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/02:06:08_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/02:06:08_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/02:06:08_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
34.810
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.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.825
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 18.219
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.077
After features/support/hooks.rb:326 0.681
After features/support/hooks.rb:100 0.000