Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 20 07 Aug 2024, 18:08

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 9:21.623 Passed
8:46.396
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.337
And no SquashFS delta is installed 0.205
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.422
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.517
When the network is plugged 0.090
And Tor is ready 22.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.447
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.322
Given I shutdown Tails and wait for the computer to power off 1:28.941
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.606
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.451
And the file system changes introduced in version 6.2~testoverlayfs are present 0.354
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.322
When the network is plugged 0.088
And Tor is ready 20.027
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.752
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 6.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.213
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 3.306
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.399
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.224
And Tor is ready 19.069
Then the Upgrader considers the system as up-to-date 0.360
# 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 15.057
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.159
After features/support/hooks.rb:326 0.906
After features/support/hooks.rb:100 0.023
35.227
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.854
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 16.223
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.479
After features/support/hooks.rb:326 0.897
After features/support/hooks.rb:100 0.000