Cucumber Reports (no 17) - Feature: Additional software

Project	Number	Date
test_Tails_ISO_18530-do-not-restart-tor	17	24 Nov 2024, 10:34

	Steps	Scenarios	Features
Additional software	76	1	2	0	0	79	4	1	5	26:28.228	Failed

Feature Additional software

As a Tails user I may want to install softwares not shipped in Tails And have them installed automatically when I enable persistence in the Greeter

Tags: @product @check_tor_leaks @slow

4:53.623

Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails

Hooks

Before features/support/hooks.rb:269 0.008

Before features/support/hooks.rb:507 0.004

Steps

Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 59.871

And I update APT using apt 12.560

And I install "popularity-contest" using apt 25.779

Then I am proposed to add the "popularity-contest" package to my Additional Software 5.127

When I create a persistent storage and activate the Additional Software feature 18.947

Then Additional Software is correctly configured for package "popularity-contest" 1.367

When I shutdown Tails and wait for the computer to power off 12.428

And I start Tails from USB drive "__internal" with network unplugged 59.886

And I enable persistence 20.793

And I log in to a new session 32.222

And the Additional Software installation service has started 41.828

Then I am notified that the installation succeeded 1.572

And Additional Software is correctly configured for package "popularity-contest" 0.940

And the package "popularity-contest" is installed after Additional Software has been started 0.297

Hooks

After features/support/hooks.rb:515 14.689

After features/support/hooks.rb:326 1.096

After features/support/hooks.rb:100 0.010

Tags: @product @check_tor_leaks @slow

2:26.645

Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package

Hooks

Before features/support/hooks.rb:269 0.006

Before features/support/hooks.rb:507 0.005

Steps

Given a computer 0.216

And I start Tails from USB drive "__internal" and I login with an administration password 1:43.836

And I update APT using apt 11.857

When I install "makepp" using apt 26.176

Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 4.487

And the package "makepp" is installed 0.070

Hooks

After features/support/hooks.rb:515 15.228

After features/support/hooks.rb:326 0.909

After features/support/hooks.rb:100 0.016

Tags: @product @check_tor_leaks @slow

5:7.698

Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic

Hooks

Before features/support/hooks.rb:269 0.005

Before features/support/hooks.rb:507 0.004

Steps

Given a computer 0.217

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 3:19.298

When I uninstall "popularity-contest" using apt 18.873

And I accept removing "popularity-contest" from Additional Software 0.853

Then "popularity-contest" is not in the list of Additional Software 0.725

When I start Synaptic 26.097

And I update APT using Synaptic 23.326

And I install "cowsay" using Synaptic 9.693

And I accept adding "cowsay" to Additional Software 1.356

Then Additional Software is correctly configured for package "cowsay" 0.928

When I uninstall "cowsay" using apt 3.264

And I refuse removing "cowsay" from Additional Software 0.566

Then Additional Software is correctly configured for package "cowsay" 0.809

When I start "Additional Software" via GNOME Activities Overview 10.611

And I remove "cowsay" from the list of Additional Software using Additional Software GUI 5.298

Then "cowsay" is not in the list of Additional Software 1.096

When I install "cowsay" using apt 3.253

And I refuse adding "cowsay" to Additional Software 0.563

Then "cowsay" is not in the list of Additional Software 0.864

Hooks

After features/support/hooks.rb:515 0.713

After features/support/hooks.rb:326 0.720

After features/support/hooks.rb:100 0.009

Tags: @product @check_tor_leaks @slow @not_release_blocker

11:44.288

Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Hooks

Before features/support/hooks.rb:269 0.004

Before features/support/hooks.rb:507 0.005

Steps

Given a computer 0.209

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:27.026

And I configure APT to prefer an old version of cowsay 0.026

When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.991

And I accept adding "cowsay" to Additional Software 6.635

And Additional Software is correctly configured for package "cowsay" 1.323

And I shutdown Tails and wait for the computer to power off 6.601

And I start Tails from USB drive "__internal" with network unplugged 1:2.972

And I enable persistence 15.537

# We need to add back this custom APT source for the Additional Software

# install step, as it was not saved in persistence

And I configure APT to prefer an old version of cowsay 0.029

# Prevent the "Warning: virtual machine detected!" notification from racing

# with the one we'll be interacting with below.

And I disable the tails-virt-notify-user.service user unit 0.079

And I log in to a new session 39.677

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.951

And I revert the APT tweaks that made it prefer an old version of cowsay 0.072

# We remove the newest package after it has been downloaded and before

# it is installed, so that the upgrade process fails

And I prepare the Additional Software upgrade process to fail 0.085

And the network is plugged 0.214

And Tor is ready 19.623

And available upgrades have been checked 0.190

And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 6.618

And I can open the Additional Software configuration window from the notification 3.213

And I shutdown Tails and wait for the computer to power off 11.377

And I start Tails from USB drive "__internal" with network unplugged 1:1.457

And I enable persistence 16.057

# We need to add back this custom APT source for the Additional Software

# install step, as it was not saved in persistence

And I configure APT to prefer an old version of cowsay 0.025

And I log in to a new session 40.583

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 2:13.834

And I revert the APT tweaks that made it prefer an old version of cowsay 0.060

And the network is plugged 0.084

And Tor is ready 1:1.728

TCA

TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:645:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:600:in `/^Tor is ready$/'
features/additional_software_packages.feature:114:in `And Tor is ready'

Then the Additional Software upgrade service has started 0.000

And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000

Hooks

After features/support/hooks.rb:515 0.036

After features/support/hooks.rb:326 14.349

Output 1

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:28:09)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_18530-do-not-restart-tor/17/artifact/build-artifacts/01:28:09_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_18530-do-not-restart-tor/17/artifact/build-artifacts/01:28:09_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_18530-do-not-restart-tor/17/artifact/build-artifacts/01:28:09_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_18530-do-not-restart-tor/17/artifact/build-artifacts/01:28:09_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:100 0.029

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

2:15.971

Scenario I am notified when Additional Software fails to install a package

Hooks

Before features/support/hooks.rb:269 0.005

Before features/support/hooks.rb:507 0.004

Steps

Given a computer 0.201

And I start Tails from USB drive "__internal" with network unplugged 1:1.577

And I enable persistence 12.885

And I remove the "cowsay" deb files from the APT cache 0.084

# Prevent the "Warning: virtual machine detected!" notification from racing

# with the one we'll be interacting with below.

And I disable the tails-virt-notify-user.service user unit 0.107

And I log in to a new session 40.420

Then I see the "The installation of your additional software failed" notification after at most 300 seconds 14.250

And I can open the Additional Software log file from the notification 5.895

And the package "cowsay" is not installed 0.549

Hooks

After features/support/hooks.rb:515 0.130

After features/support/hooks.rb:326 1.231

After features/support/hooks.rb:100 0.011

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Additional software	76	1	2	0	0	79	4	1	5	26:28.228	Failed

Feature Report