launchpad-buildd processes stderr/stdout very suboptimally
Bug #804978 reported by
Adam Conrad
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
launchpad-buildd |
Triaged
|
High
|
Unassigned |
Bug Description
Builds that produce a large amount of log output take significantly longer (like, several orders of magnitude) on launchpad-buildd than they do using raw sbuild from the lp-buildd source. Fairly trivially reproduced by taking a simple package (say "hello") and tossing a for loop in debian/rules that throws a few thousand (or million, if testing on a fast machine) lines to stdout. sbuild or dpkg-buildpackage teeing a log to disk will have no real issues with this, lp-buildd will swap like crazy and flirt with bringing your machine down.
Julian and I talked about this at the Platform Rally, and he said he'd look at it and maybe cargo-cult some code from buildd-manager or some such.
To post a comment you must log in.
(And as discussed previously, this is affecting us real-world right now, where I have a ludicrously long test timeout for a telepathy-glib test that executes in about 12s on a manual build on the same hardware, while taking several minutes on lp-buildd, obviously I can't/won't push patches upstream to extend test timeouts for the sake of our slightly nutty buildds)