Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 47 18 Apr 2024, 22:54

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 7:56.108 Passed
7:22.921
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.235
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
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.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.037
And Tor is ready 19.315
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.491
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.917
Given I shutdown Tails and wait for the computer to power off 1:4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.160
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.289
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.335
When the network is plugged 0.078
And Tor is ready 16.429
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.252
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.309
Given I shutdown Tails and wait for the computer to power off 4.729
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.435
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.890
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.031
And Tor is ready 17.298
Then the Upgrader considers the system as up-to-date 10.675
# 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 14.864
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.932
After features/support/hooks.rb:305 0.748
After features/support/hooks.rb:89 0.019
33.186
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 8.955
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.058
And the signing key used by the Upgrader is outdated 0.840
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 16.245
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.727
After features/support/hooks.rb:305 1.550
After features/support/hooks.rb:89 0.000