Bug #9901

Vagrant fails to build Tails in RAM

Added by anonym 2015-08-05 08:35:45 . Updated 2015-08-11 10:41:30 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Build system
Target version:
Tails_1.5
Start date:
2015-08-05
Due date:
% Done:

100%

Feature Branch:
bugfix/9901-bump-vagrant-ram-for-ram-builds
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

I fail to build devel in RAM using Vagrant as of commit:0525d22 due to lack of space on the ram disk, at I think 98% of the squashing process. Likely it’s due to the increased size of Tor Browser 5.0a4 that was recently added.

Subtasks

History

#1 Updated by anonym 2015-08-05 09:30:41

Currently we need 6656 + 512 = 7 GiB of RAM for this, which makes it more or less possible for systems with 8 GiB of RAM to build Tails like this. Since it fails at 98%, we likely only need perhaps 50 MiB or so more, but I’m sure we’ll soon need more again and we’ll be back. 512 MiB feels more future-proof, perhaps even until we’re based on Jessie, but that makes building Tails with 8 GiB of system RAM quite hard. Or perhaps swapping out most of the host OS still makes it possible?

#2 Updated by intrigeri 2015-08-06 09:20:21

  • Subject changed from vagrant fails to build Tails in RAM to Vagrant fails to build Tails in RAM
  • Assignee set to anonym

anonym, can you take this one? As said on IRC, I recommend merging current testing into feature/jessie, and bumping the needed memory as much as needed to build the resulting feature/jessie.

#3 Updated by anonym 2015-08-07 14:59:06

I did some bisecting. I can build feature/jessie with BUILD_SPACE_REQUIREMENT = 6656 + 256 + 128 - 64 - 32 but it fails with an additional - 16. I didn’t bother bisecting further. So it seems 6944 is the magic number, which means we in total need 6944 + 512 = 7456 MiB. Hence a system with 8 GiB of RAM couldn’t run many other processes (Xorg etc) to be able to build Tails in RAM. Do we really expect anyone to need this, or should we just bump to 7 GiB like in feature/jessie?

#4 Updated by intrigeri 2015-08-08 01:22:40

> Hence a system with 8 GiB of RAM couldn’t run many other processes (Xorg etc) to be able to build Tails in RAM. Do we really expect anyone to need this, or should we just bump to 7 GiB like in feature/jessie?

I would go for 7 GiB in testing. One with 8 GB of RAM can still either:

  • build in RAM, and some of the build will force swap IO;
  • build on disk.

#5 Updated by anonym 2015-08-08 04:13:04

  • Status changed from Confirmed to In Progress

Applied in changeset commit:c1d0b6adc0ca99cdfdd86151eb54684d90c42658.

#6 Updated by anonym 2015-08-08 04:14:21

  • Assignee changed from anonym to intrigeri
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to bugfix/9901-bump-vagrant-ram-for-ram-builds

Then I go with 7 GiB. Please review’n’merge into testing and devel!

#7 Updated by intrigeri 2015-08-08 04:36:12

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Applied in changeset commit:58fab07725ff47d0c38140a84f292b97673b3f19.

#8 Updated by intrigeri 2015-08-08 04:37:41

  • Assignee deleted (intrigeri)
  • QA Check changed from Ready for QA to Pass

Done. Also merged into experimental. Not merged into feature/jessie since I’m waiting for anonym to do clever conflict resolution in there.

#9 Updated by BitingBird 2015-08-11 10:41:30

  • Status changed from Fix committed to Resolved