Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 31 27 Nov 2024, 21:12

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:41.649 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:5.553
Before features/support/hooks.rb:269 0.006
Given a computer 0.234
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 28.860
When I start Tails from USB drive "old" with network unplugged 1:31.353
Then the boot device has safe access rights 2.983
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.722
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.103
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:24.499
Then Tails is running from USB drive "old" 0.340
And I create a persistent partition 33.114
And I take note of which tps features are available 1.864
Then a Tails persistence partition exists on USB drive "old" 0.799
And I shutdown Tails and wait for the computer to power off 8.299
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.388
Before features/support/hooks.rb:269 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.921
Then Tails is running from USB drive "old" 0.489
And all tps features are active 2.018
When I write some files expected to persist 1.671
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.737
And I take note of which tps features are available 0.791
And I shutdown Tails and wait for the computer to power off 4.413
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.509
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.013
Tags: @product
2:32.037
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 10.713
And I log in to a new session 19.632
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.648
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.533
Then the running Tails is installed on USB drive "to_upgrade" 18.635
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 6.785
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.775
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.151
Then all tps features from the old Tails version are active 1.657
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.475
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 2.457
After features/support/hooks.rb:326 0.859
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
23:18.495
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 26.683
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.069
And Tor is ready 18.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.813
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.166
Given I shutdown Tails and wait for the computer to power off 10.991
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:1.249
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.828 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:07:12)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/31/artifact/build-artifacts/02:07:12_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/31/artifact/build-artifacts/02:07:12_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/31/artifact/build-artifacts/02:07:12_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
33.296
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.775
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 1.050
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 16.585
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.297
After features/support/hooks.rb:326 1.090
After features/support/hooks.rb:100 0.000