| ricotz | hello :), I am wondering if this build is stuck or still working hard in the background? https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.1~rc2-0ubuntu1/+build/21083931 | 06:40 |
|---|---|---|
| ricotz | same for https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.1~rc2-0ubuntu1/+build/21083932 | 06:41 |
| === icey_ is now known as icey | ||
| cjwatson | ricotz: I can't say, don't know this package's build system well enough | 10:04 |
| cjwatson | ricotz: IIRC that sort of thing is normally a pkgbinarymangler bug of some kind | 10:05 |
| rainmanp7 | . | 10:49 |
| ricotz | cjwatson, I see, it seems it hasn't moved in the last hours, could you cancel and restart both? | 10:57 |
| cjwatson | ricotz: cancelled, do you want to grab build logs for inspection before I retry? | 10:59 |
| ricotz | cjwatson, grabbed them both, please proceed :) | 11:00 |
| cjwatson | ricotz: done | 11:15 |
| ricotz | cjwatson, thank you | 11:37 |
| === hellswor1 is now known as hellsworth | ||
| === ijohnson is now known as ijohnson|lunch | ||
| === ijohnson|lunch is now known as ijohnson | ||
| ricotz | cjwatson, if you are still around, please cancel and restart https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.1~rc2-0ubuntu1/+build/21083933 | 22:51 |
| cjwatson | ricotz: can cancel; is there any reason to believe a retry will work? | 22:51 |
| ricotz | cjwatson, the previous retry for amd64 worked | 22:51 |
| ricotz | the other arm64 is still running | 22:52 |
| ricotz | this might be triggered by the recent load on the builders, and calmed down afaics | 22:53 |
| cjwatson | ricotz: hm, OK, retried. I think it's more likely to be some kind of occasional race in pkgstripfiles (perhaps when run in parallel?), but not sure | 22:54 |
| RikMills | there are a few KDE packages that sometimes do that 'INFO: pkgstripfiles: waiting for lock' for quite a long time. they do eventually break that loop and finish | 22:55 |
| cjwatson | I've also seen it apparently run forever | 22:56 |
| cjwatson | it may be subtle in a way I don't currently understand | 22:56 |
| RikMills | I'm glad I have not had that then | 22:56 |
| cjwatson | (forever as in I noticed builds that had been running for a week stuck there) | 22:56 |
| RikMills | O_O | 22:56 |
| ricotz | cjwatson, the interesting part of the earlier amd64 log is https://paste.debian.net/plain/1187130 | 22:56 |
| cjwatson | I realize this is not an astronomical or theological definition of forever but still :) | 22:56 |
| RikMills | longer that humanly tolerable.... | 22:57 |
| RikMills | *than | 22:57 |
| cjwatson | ricotz: ah yes, that looks rather like bad error handling then, one would think it should have given up there | 22:57 |
| cjwatson | (leaving aside whatever caused that error to start with, which isn't obvious to me) | 22:58 |
| ricotz | cjwatson, there are disk space issues in the past, which the packaging has a mitigation for, but not sure if this gets hit again due the mangler | 23:00 |
| ricotz | cjwatson, thank you for restarting | 23:01 |
| ricotz | cjwatson, jfyi the other logs contain the "same" error | 23:09 |
| tsimonq2 | Completed builds 290915 successful 49178 failed. | 23:43 |
| tsimonq2 | We certainly don't need all of this data. | 23:44 |
| tsimonq2 | I'm not seeing a way I can just delete old builds - does the Launchpad tooling do this by itself? | 23:44 |
| cjwatson | Can you be more specific? | 23:45 |
| cjwatson | And why is it important? | 23:46 |
| tsimonq2 | It isn't important, I would just like to be somewhat thoughtful when the Lubuntu CI pumps out many, many builds per day. It's extremely useful for us in Lubuntu development, but we really don't need old build logs and artifacts from more than a week ago at best. | 23:48 |
| tsimonq2 | I'm referring to the PPAs under ~lubuntu-ci. | 23:48 |
| cjwatson | Artifacts are automatically garbage-collected after a while when they're no longer published (in public PPAs, anyway). | 23:48 |
| cjwatson | We generally keep things like old build logs forever. It's not particularly expensive for us to do so, and they're the sort of thing that's often unpredictably useful years later when doing some kind of archaeology. | 23:49 |
| cjwatson | If we didn't GC artifacts that would indeed become a problem for us much more quickly, but build logs are on average rather smaller. | 23:50 |
| cjwatson | There's no way to manually delete old builds. | 23:50 |
| cjwatson | (Short of SQL surgery on our part, which is much more expensive in terms of human time ...) | 23:50 |
| tsimonq2 | That answers my query; if sysadmins are ever looking at things and it becomes a problem over a couple of years, feel free to purge those old logs. If it's not much of a nuisance then it looks like we're fine for now. | 23:50 |
| tsimonq2 | I understand if it would take more work than it's worth. :) | 23:51 |
| cjwatson | I can say with some confidence that build logs are unlikely to be anywhere near the first place we go looking for space :-) | 23:51 |
| tsimonq2 | Sounds good, thanks cjwatson. :) | 23:51 |
| cjwatson | Out of curiosity let me see if I can figure out how much space your build logs are currently using ... | 23:52 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!