Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 52 23 Apr 2024, 06:48

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:52.840 Passed
6:13.831
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 11.322
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.640
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.050
And Tor is ready 21.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.234
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.584
Given I shutdown Tails and wait for the computer to power off 8.822
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.482
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.073
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.242
When the network is plugged 0.032
And Tor is ready 19.625
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.367
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.407
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.840
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.001
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.051
And Tor is ready 16.269
Then the Upgrader considers the system as up-to-date 0.344
# 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.909
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.940
After features/support/hooks.rb:305 0.707
After features/support/hooks.rb:89 0.033
39.009
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.206
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.515
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.665
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 19.989
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.508
After features/support/hooks.rb:305 0.774
After features/support/hooks.rb:89 0.000