Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 42 14 Apr 2024, 06:30

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:23.855 Passed
5:51.716
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.060
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
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.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.033
And Tor is ready 18.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.666
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.705
Given I shutdown Tails and wait for the computer to power off 6.544
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.558
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.082
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.277
When the network is plugged 0.057
And Tor is ready 17.382
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.174
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.456
Given I shutdown Tails and wait for the computer to power off 4.463
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.284
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.066
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.404
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.037
And Tor is ready 18.914
Then the Upgrader considers the system as up-to-date 0.254
# 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.301
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.831
After features/support/hooks.rb:305 0.731
After features/support/hooks.rb:89 0.017
32.139
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.687
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the signing key used by the Upgrader is outdated 0.995
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 14.233
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.727
After features/support/hooks.rb:305 1.027
After features/support/hooks.rb:89 0.000