Bug #11582

Some upgrade test scenarios fail due to lack of disk space on Jenkins

Added by intrigeri 2016-07-21 02:56:49 . Updated 2016-09-20 16:50:08 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_2.6
Start date:
2016-07-21
Due date:
% Done:

100%

Feature Branch:
bugfix/11590-installer-robustness
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:
280

Description

Once Bug #10720 is mostly workaround’ed, usb_install.feature passes but then two of the upgrade scenarios fail with:

    And I start Tails from DVD with network unplugged and I login   # features/step_definitions/common_steps.rb:191
    And I temporarily create a 4 GiB disk named "pristine"          # features/step_definitions/common_steps.rb:139
      Error creating disk "pristine" in "/tmp/TailsToaster/TailsToasterStorage". Need 4096 MiB but only 4115 MiB is available of which 500 MiB is reserved for other temporary files.
      <false> is not true. (Test::Unit::AssertionFailedError)
      ./features/support/helpers/storage_helper.rb:94:in `create_new_disk'
      ./features/step_definitions/common_steps.rb:140:in `/^I (temporarily )?create a (\d+) ([[:alpha:]]+) disk named "([^"]+)"$/'
      features/usb_upgrade.feature:17:in `And I temporarily create a 4 GiB disk named "pristine"'

The affected scenarios are:

  • Try to “Upgrade from ISO” Tails to a pristine USB drive
  • Try to “Upgrade from ISO” Tails to a USB drive with GPT and a FAT partition

See e.g. https://jenkins.tails.boum.org/job/test_Tails_ISO_bugfix-10720-installer-freezes-on-jenkins/39/.

See Feature #10503 for our previous results about peak disk usage. Maybe we should add usb_upgrade.feature to prioritized_features, to make it run earlier?

Subtasks

Related issues

Related to Tails - Feature #10503: Run erase_memory.feature first to optimize test suite performance Resolved 2015-11-06
Has duplicate Tails - Bug #11618: Tmpdir too small on isotesters Duplicate 2016-08-01
Blocked by Tails - Bug #11590: Improve Tails Installer robustness for 2.6 Resolved 2016-07-22

History

#1 Updated by intrigeri 2016-07-21 02:57:11

  • related to Feature #10503: Run erase_memory.feature first to optimize test suite performance added

#2 Updated by intrigeri 2016-07-21 02:57:41

  • related to Bug #10720: Tails Installer freezes when calling system_partition.call_set_name_sync in partition_device added

#3 Updated by intrigeri 2016-07-21 03:08:17

  • Assignee set to intrigeri
  • Target version set to Tails_2.6
  • Deliverable for set to SponsorS_Internal

I’ll give it a try.

#4 Updated by intrigeri 2016-07-22 01:34:21

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 50
  • Feature Branch set to bugfix/10720-installer-freezes-on-jenkins

Fixed on bugfix/10720-installer-freezes-on-jenkins.

#5 Updated by intrigeri 2016-07-22 01:34:31

  • related to deleted (Bug #10720: Tails Installer freezes when calling system_partition.call_set_name_sync in partition_device)

#6 Updated by intrigeri 2016-07-22 01:34:41

  • blocked by Bug #10720: Tails Installer freezes when calling system_partition.call_set_name_sync in partition_device added

#7 Updated by intrigeri 2016-07-22 04:00:11

  • blocks deleted (Bug #10720: Tails Installer freezes when calling system_partition.call_set_name_sync in partition_device)

#8 Updated by intrigeri 2016-07-22 04:00:21

  • blocked by Bug #11590: Improve Tails Installer robustness for 2.6 added

#9 Updated by intrigeri 2016-07-22 04:00:39

  • Feature Branch changed from bugfix/10720-installer-freezes-on-jenkins to bugfix/11590-installer-robustness

#10 Updated by intrigeri 2016-07-22 04:09:02

  • Assignee changed from intrigeri to anonym
  • QA Check set to Ready for QA

#11 Updated by intrigeri 2016-08-01 13:15:19

  • has duplicate Bug #11618: Tmpdir too small on isotesters added

#12 Updated by anonym 2016-08-23 08:27:59

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

#13 Updated by anonym 2016-09-20 16:50:08

  • Status changed from Fix committed to Resolved