Merge lp://qastaging/~pfalcon/linaro-android-build-tools/disk-space-monitor into lp://qastaging/linaro-android-build-tools
Proposed by
Paul Sokolovsky
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merged at revision: | 394 | ||||
| Proposed branch: | lp://qastaging/~pfalcon/linaro-android-build-tools/disk-space-monitor | ||||
| Merge into: | lp://qastaging/linaro-android-build-tools | ||||
| Diff against target: |
88 lines (+38/-14) 2 files modified
build-scripts/build-android (+2/-0) node/build (+36/-14) |
||||
| To merge this branch: | bzr merge lp://qastaging/~pfalcon/linaro-android-build-tools/disk-space-monitor | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Данило Шеган (community) | Approve | ||
| Alexander Sack | Pending | ||
| Linaro Infrastructure | Pending | ||
|
Review via email:
|
|||
Description of the change
This bumps ramdisk size to 11.75Gb (previous abs maximum), adds df at the end of build, and allow to specify RAMDISK_SIZE for a build (0 disables it).
Well, as Andy Doan hinted that current cascade of failures is likely related to kernel objects drop into build/out/ , I don't hold my breath that 11.75Gb will help, likely will need to limit ramdisk to build/out/target/ . But so far running as such: https:/
To post a comment you must log in.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
As discussed on IRC, when RAMDISK_SIZE is not set, we keep the previous behaviour. It would be nice to do a drive-by fix to make code make sense when read in the second `test .. -gt 10 gig` to actually be `test -gt 12582912` (i.e. 12gb).