> Hi Dann,
> On Mon, Mar 13, 2017 at 11:12:23AM -0600, dann frazier wrote:
>> Just a guess - but maybe the build has exhausted the builder's
>> memory? If so, you might be able to workaround it by restricting the
>> parallel level. I can't offer an explanation as to why it started
>> occurring with this upload. Assuming nothing about the builder memory
>> config has changed, you might need to compare memory usage profiles w/
>> an older build environment to look for red flags.
> Looks like you are right.
> I managed to reproduce this locally, and I get this:
> [15746515.856452] Out of memory: Kill process 2148 (sed) score 553 or sacrifice child
> [15746515.857476] Killed process 2148 (sed) total-vm:1180204kB, anon-rss:1167084kB, file-rss:0kB
> FWIW, the sed script is 2.6M and 13692 lines, and DEBIAN/md5sums is 3.2M and
> 29035 lines.
> However I do not understand what 'parallel level' you are talking about.
> If it is the package build parallel level, then it is unrelated — what gets
> killed is a single sed command ("sed -i -f $sedscript DEBIAN/md5sums").
Yeah, I was referring to the package build parallel level. Reason
being, if there are other commands running at the same time, they
maybe using some memory that this sed command could have otherwise
> The only workaround I can apply is disabling the PNGs compression by
> exporting NO_PNG_PKG_MANGLE=1.
Yep, or that :)
ubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel