Project Number Date
test_Tails_ISO_stable 4629 22 Jan 2024, 15:45

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:25.300 Passed
5:57.761
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.896
And no SquashFS delta is installed 0.297
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.396
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.054
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.421
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.564
When the network is plugged 0.055
And Tor is ready 15.075
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.693
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.254
Given I shutdown Tails and wait for the computer to power off 6.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.793
Then Tails is running version 2.2~testoverlayfsng 0.102
And all tps features are active 2.133
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.461
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.320
When the network is plugged 0.034
And Tor is ready 15.466
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.764
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.266
Given I shutdown Tails and wait for the computer to power off 4.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.257
Then Tails is running version 2.3~testoverlayfsng 0.138
And all tps features are active 2.263
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.610
And only the 2.3~testoverlayfsng 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.337
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.339
When the network is plugged 0.047
And Tor is ready 17.689
Then the Upgrader considers the system as up-to-date 0.739
# 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 26.606
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.473
After features/support/hooks.rb:291 0.873
After features/support/hooks.rb:75 0.025
27.539
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.206
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.363
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.069
And the signing key used by the Upgrader is outdated 0.699
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 14.480
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.681
After features/support/hooks.rb:291 0.654
After features/support/hooks.rb:75 0.000