Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 97 07 Jun 2024, 06:37

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@automatic_upgrade 43 0 0 0 0 43 2 0 2 6:40.563 Passed
6:8.570
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 10.587
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.048
And Tor is ready 18.036
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.365
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.696
Given I shutdown Tails and wait for the computer to power off 8.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.083
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.075
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.395
# 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.221
When the network is plugged 0.044
And Tor is ready 19.055
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.902
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.473
Given I shutdown Tails and wait for the computer to power off 4.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.619
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.075
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.036
And Tor is ready 18.752
Then the Upgrader considers the system as up-to-date 0.299
# 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.393
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.846
After features/support/hooks.rb:315 0.748
After features/support/hooks.rb:100 0.015
31.993
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.295
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.937
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 15.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.398
After features/support/hooks.rb:315 0.674
After features/support/hooks.rb:100 0.000