| 1 |
Am 03.06.2015 um 22:32 schrieb Ciaran McCreesh: |
| 2 |
> On Wed, 03 Jun 2015 22:22:39 +0200 |
| 3 |
>> i've just hit the constraint CHECKREQS_MEMORY=3G in |
| 4 |
>>> =www-client/chromium-44.* on a 2 GiB RAM machine.. (having |
| 5 |
>>> additionally |
| 6 |
>> 5G Swap on SSD..) |
| 7 |
>> |
| 8 |
>> I personally doubt that check-reqs_memory() in the eclass should only |
| 9 |
>> check for *physical* rather than *virtual* RAM to fulfill this |
| 10 |
>> constraint and fail if unsatisfied. |
| 11 |
> |
| 12 |
> Swap is horrifically slow. It's better to fail than to use swap for |
| 13 |
> stuff... |
| 14 |
> |
| 15 |
(basically) agreed - but in distcc/icecream/whatever builds, linking |
| 16 |
*may* also be done on remote machines, which *may* fulfill the memory |
| 17 |
constraint.. |
| 18 |
we're talking about *build* constraints rather than *run* constraints, |
| 19 |
right..? |
| 20 |
|
| 21 |
Christian |
Archives