Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 70 10 May 2024, 06:51

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 8:24.695 Passed
7:44.226
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.733
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.523
When the network is plugged 0.368
And Tor is ready 23.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.409
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.937
Given I shutdown Tails and wait for the computer to power off 1:20.869
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.003
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.495
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.409
# 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.282
When the network is plugged 0.040
And Tor is ready 20.859
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.232
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.060
Given I shutdown Tails and wait for the computer to power off 4.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.571
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 4.380
And the file system changes introduced in version 6.3~testoverlayfs are present 0.544
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.037
And Tor is ready 17.691
Then the Upgrader considers the system as up-to-date 0.312
# 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.795
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.040
After features/support/hooks.rb:305 1.030
After features/support/hooks.rb:89 0.021
40.468
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.804
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.056
And the signing key used by the Upgrader is outdated 0.951
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 21.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.650
After features/support/hooks.rb:305 0.655
After features/support/hooks.rb:89 0.000