buildds have different resources (e.g. RAM, disk space) and there is no way to make sure build needing such a resource runs on a buildd with the resource
Bug #684395 reported by
fijal
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When scheduling a build, there is no way to say how much resources you need. This is a problem for PyPy, which requires quite a bit of memory (1.2G for 32bit, 2.4G for 64bit roughly) and means build crashes every now and then and every now and then succeeds.
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
| Changed in soyuz: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| tags: | added: buildfarm soyuz-build |
| Changed in launchpad: | |
| importance: | Wishlist → Low |
| tags: | added: feature |
| summary: |
- PPA machines have different resources and there is no way to choose one + buildds have different resources (e.g. RAM, disk space) and there is no + way to make sure build needing such a resource runs on a buildd with the + resource |
To post a comment you must log in.
I have a feeling this might be a dupe but I can't find the bug I am thinking of. The closest is bug 3355.
Basically what we need to do is have a builder capability versus package requirements set-up, that allows intelligent builder choice. This is going to be quite hard to implement though.