Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 29 19 Dec 2024, 00:34

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 85 1 1 0 0 87 6 1 7 18:38.580 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:59.863
Before features/support/hooks.rb:269 0.005
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.748
When I start Tails from USB drive "old" with network unplugged 1:21.879
Then the boot device has safe access rights 3.010
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.524
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.532
Before features/support/hooks.rb:269 0.004
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:21.386
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 33.121
And I take note of which tps features are available 1.518
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.140
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.783
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.042
Then Tails is running from USB drive "old" 0.727
And all tps features are active 1.955
When I write some files expected to persist 1.745
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.246
And all persistence configuration files have safe access rights 0.485
And all persistent directories from the old Tails version have safe access rights 2.423
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 4.294
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.263
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.474
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.595
And I log in to a new session 18.231
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.723
And I plug USB drive "to_upgrade" 2.525
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.911
Then the running Tails is installed on USB drive "to_upgrade" 25.061
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 3.551
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.263
Before features/support/hooks.rb:269 0.005
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.916
Then all tps features from the old Tails version are active 1.488
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.585
And the expected persistent files created with the old Tails version are present in the filesystem 1.427
And all persistent directories from the old Tails version have safe access rights 2.330
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:13.625
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.674
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.069
And Tor is ready 25.385
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.059
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.437
Given I shutdown Tails and wait for the computer to power off 8.613
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.271
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.174
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.118
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.443
# 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.389
When the network is plugged 0.067
And Tor is ready 17.106
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.616
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.939
Given I shutdown Tails and wait for the computer to power off 4.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.211
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.960
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.311
When the network is plugged 0.072
And Tor is ready 20.531
Then the Upgrader considers the system as up-to-date 0.309
# 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 0.000
undefined 
undefined local variable or method `options' for #<Object+RSpec::Matchers+Cucumber::RbSupport::RbWorld+PCAPRUB+Test::Unit::Assertions+PP::ObjectMixin+JSON::Ext::Generator::GeneratorMethods::Object+Kernel:0x1b634> (NameError)
./features/step_definitions/common_steps.rb:1109:in `launch_unsafe_browser'
./features/step_definitions/browser.rb:61:in `/^I (try to )?start the Unsafe Browser$/'
./features/step_definitions/browser.rb:65:in `/^I successfully start the Unsafe Browser(?: in "([^"]+)")?$/'
features/usb_upgrade.feature:122:in `And I successfully start the Unsafe Browser'
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:326 5.075 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:43:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/29/artifact/build-artifacts/01:43:35_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/29/artifact/build-artifacts/01:43:35_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/29/artifact/build-artifacts/01:43:35_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/29/artifact/build-artifacts/01:43:35_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.037
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.297
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.739
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 20.982
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.463
After features/support/hooks.rb:326 0.721
After features/support/hooks.rb:100 0.000