Project Number Date
test_Tails_ISO_devel 4115 11 Dec 2025, 13:42

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 84 1 2 0 0 87 6 1 7 18:46.860 Failed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
1:58.065
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.854
When I start Tails from USB drive "old" with network unplugged 1:21.211
Then the boot device has safe access rights 3.542
And Tails is running from USB drive "old" 0.419
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:331 3.994
After features/support/hooks.rb:100 0.012
Tags: @product
2:54.928
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:29.722
Then Tails is running from USB drive "old" 0.775
And I create a persistent partition 45.319
And I take note of which tps features are available 8.831
Then a Tails persistence partition exists on USB drive "old" 3.788
And I shutdown Tails and wait for the computer to power off 26.289
After features/support/hooks.rb:331 0.300
After features/support/hooks.rb:100 0.011
Tags: @product
3:27.735
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 5.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:48.172
Then Tails is running from USB drive "old" 0.316
And all tps features are active 2.013
When I write some files expected to persist 1.731
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.352
And all persistent directories from the old Tails version have safe access rights 3.172
And I take note of which tps features are available 26.658
Command 
Command failed: /usr/local/lib/tpscli get-features
error code: 1
stdout: 
stderr: Call failed: Connection timed out
Traceback (most recent call last):
  File "<string>", line 1, in <module>
    import sys, json; print(json.dumps(json.load(sys.stdin)['data'][0]))
                                       ~~~~~~~~~^^^^^^^^^^^
  File "/usr/lib/python3.13/json/__init__.py", line 293, in load
    return loads(fp.read(),
        cls=cls, object_hook=object_hook,
        parse_float=parse_float, parse_int=parse_int,
        parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
  File "/usr/lib/python3.13/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
           ~~~~~~~~~~~~~~~~~~~~~~~^^^
  File "/usr/lib/python3.13/json/decoder.py", line 345, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
               ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/json/decoder.py", line 363, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/usb.rb:55:in `tps_features'
./features/step_definitions/usb.rb:1084:in `/^I take note of which tps features are available$/'
features/usb_upgrade.feature:54:in `And I take note of which tps features are available'
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:331 5.899 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:29:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4115/artifact/build-artifacts/01:29:41_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4115/artifact/build-artifacts/01:29:41_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4115/artifact/build-artifacts/01:29:41_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/4115/artifact/build-artifacts/01:29:41_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.012
Tags: @product
4:10.964
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.031
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 38.923
And I log in to a new session 36.014
And I clone USB drive "old" to a new USB drive "to_upgrade" 35.415
And I plug USB drive "to_upgrade" 2.925
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.876
Then the running Tails is installed on USB drive "to_upgrade" 19.380
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:331 3.606
After features/support/hooks.rb:100 0.000
Tags: @product
1:27.493
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:18.935
Then all tps features from the old Tails version are active 1.472
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 2.862
And the expected persistent files created with the old Tails version are present in the filesystem 1.401
And all persistent directories from the old Tails version have safe access rights 2.267
After features/support/hooks.rb:331 0.883
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
4:23.400
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.419
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.060
And Tor is ready 13.782
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.838
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.196
Given I shutdown Tails and wait for the computer to power off 11.234
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.867
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.449
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.210
When the network is plugged 0.062
And Tor is ready 13.684
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.580
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.996
Given I shutdown Tails and wait for the computer to power off 8.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.975
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.887
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.051
And Tor is ready 12.338
Then the Upgrader considers the system as up-to-date 0.115
# 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 6.287
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.473
After features/support/hooks.rb:331 0.952
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
24.273
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.529
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 10.577
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.730
After features/support/hooks.rb:331 1.032
After features/support/hooks.rb:100 0.000