Re: pkgstripfiles killed during build
On Wed, Mar 15, 2017 at 10:15 AM, Dmitry Shachnev wrote: > Hi Dann, > > On Mon, Mar 13, 2017 at 11:12:23AM -0600, dann frazier wrote: >> Dmitry, >> 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 used. > The only workaround I can apply is disabling the PNGs compression by > exporting NO_PNG_PKG_MANGLE=1. Yep, or that :) -dann -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: pkgstripfiles killed during build
Hi Dann, On Mon, Mar 13, 2017 at 11:12:23AM -0600, dann frazier wrote: > Dmitry, > 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”). The only workaround I can apply is disabling the PNGs compression by exporting NO_PNG_PKG_MANGLE=1. -- Dmitry Shachnev signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: pkgstripfiles killed during build
On Fri, Mar 10, 2017 at 8:30 AM, Dmitry Shachnev wrote: > Hi all, > > I get a strange error with “mathjax” package on Ubuntu buildds. > > One of the binary packages (fonts-mathjax-extras) contains a lot of small > PNG files. And with the last upload (2.7.0-2) I get this [1]: > > pkgstripfiles: Running PNG optimization (using 4 cpus) for package > fonts-mathjax-extras ... > [...] > > .o...o.o..o..ooo...o.ooo.o.oo.ooo..oo.....o...o..o...oo.o.ooo..oo.o..oo..oo..o.oo.o...o > /usr/bin/pkgstripfiles: line 63: 21195 Killed sed -i -f > $sedscript DEBIAN/md5sums > dh_builddeb.pkgbinarymangler: dpkg-deb --build debian/fonts-mathjax-extras > .. returned exit code 137 >dpkg-genchanges --build=any,all -mLaunchpad Build Daemon > >../mathjax_2.7.0-2_amd64.changes > dpkg-genchanges: info: binary-only upload (no source code included) > dpkg-genchanges: error: cannot fstat file > ../fonts-mathjax-extras_2.7.0-2_all.deb: No such file or directory > dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2 > > I tried retrying the build a couple of times, it did not help. > > With the previous upload (2.7.0-1) it was fine [2], and the last upload did > not make any changes to the PNG files. > > Does anybody know why this may be happening? Dmitry, 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. -dann -dann -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
