Project Number Date
test_Tails_ISO_stable 4958 20 Jul 2024, 12:43

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:11.780 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:59.545
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.802
When I start Tails from USB drive "old" with network unplugged 1:25.600
Then the boot device has safe access rights 2.900
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.578
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.003
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:26.293
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 30.890
And I take note of which tps features are available 1.547
Then a Tails persistence partition exists on USB drive "old" 0.700
And I shutdown Tails and wait for the computer to power off 8.074
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.033
Before features/support/hooks.rb:269 0.007
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.982
Then Tails is running from USB drive "old" 0.352
And all tps features are active 1.935
When I write some files expected to persist 1.611
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.746
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.320
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 22.764
After features/support/hooks.rb:326 0.082
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.225
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 9.972
And I log in to a new session 17.319
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.251
And I plug USB drive "to_upgrade" 2.335
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.923
Then the running Tails is installed on USB drive "to_upgrade" 16.024
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 6.472
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.998
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.020
Then all tps features from the old Tails version are active 1.630
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 2.973
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.472
After features/support/hooks.rb:326 0.971
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
23:17.722
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 28.286
And no SquashFS delta is installed 0.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.462
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.057
And Tor is ready 16.961
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.769
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.192
Given I shutdown Tails and wait for the computer to power off 19.532
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:52.505
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:706:in `new'
./features/step_definitions/common_steps.rb:706:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:292: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.867 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:03:44)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4958/artifact/build-artifacts/02:03:44_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4958/artifact/build-artifacts/02:03:44_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4958/artifact/build-artifacts/02:03:44_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
31.250
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 9.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.880
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 14.484
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.362
After features/support/hooks.rb:326 0.782
After features/support/hooks.rb:100 0.000