| === jamesh_ is now known as jamesh | ||
| alakx | Hei | 02:21 |
|---|---|---|
| alakx | im getting an error: Oops! | 02:21 |
| alakx | Sorry, something just went wrong in Launchpad. | 02:21 |
| alakx | while trying to login | 02:21 |
| alakx | (Error ID: OOPS-e49f64ec98a62bc9e53566b7bed5a8a6) | 02:22 |
| ubot5 | https://oops.canonical.com/?oopsid=OOPS-e49f64ec98a62bc9e53566b7bed5a8a6 | 02:22 |
| alakx | yes | 02:22 |
| cjwatson | alakx: Sorry about that - I've fixed your account, so it should work now | 06:56 |
| alakx | cjwatson, thank you | 09:34 |
| Laney | interested in https://launchpad.net/ubuntu/+source/geary/3.38.0.1-1/+build/19944657 ? or is this a w_grant thing? | 11:41 |
| Laney | (don't retry, it's going to ftbfs) | 11:41 |
| cjwatson | Laney: Wow, that builder is sad | 11:53 |
| cjwatson | [4105202.978131] systemd-journald[379]: Failed to write entry (25 items, 659 bytes) despite vacuuming, ignoring: Bad message | 11:53 |
| * cjwatson reboots it | 11:53 | |
| cjwatson | Laney: Do you mean it will FTBFS even if it gets past this error? | 11:54 |
| Laney | cjwatson: Yeah | 11:57 |
| cjwatson | Laney: I've fixed that builder. Let us know if you see that error on others | 11:57 |
| Laney | I mean, you can retry if you want for testing, but it won't get us a successful build, so don't do it to try to help | 11:57 |
| Laney | roger, cheers | 11:57 |
| cjwatson | I think maybe its RTC was Very Wrong? Hard to tell because it wouldn't let me log in | 11:57 |
| cjwatson | (At least not without changing the root password, which I didn't really want to do) | 11:57 |
| gpiccoli | o/ cjwatson - sorry to annoy, I'm curious about something. Do you know why ppc64el builders are so likely to get stuck in the cleaning stage? | 12:38 |
| gpiccoli | We have some there, cleaning... | 12:38 |
| gpiccoli | not all of them, but a considerable amount | 12:38 |
| cjwatson | I mean. scalingstack | 12:43 |
| cjwatson | Depends on reliability of a whole bunch of openstack components and the relevant hardware | 12:43 |
| cjwatson | We occasionally go through and burn a couple of hours of SRE time on spot-debugging things | 12:43 |
| cjwatson | I don't have a general answer for you | 12:44 |
| alakx | how many CPU threads does the builder usually have? | 12:48 |
| alakx | if i set it for 16 for example, would it be a overkill ? | 12:48 |
| cjwatson | alakx: In the Launchpad build farm, you mean? They're mostly VMs with 4 cores | 12:53 |
| alakx | cjwatson, i see. so if i would like the builder to run some tests then 4 threads should be maximum | 12:54 |
| cjwatson | That would probably be wise | 12:55 |
| cjwatson | In general it's usually best for packages to detect the number of cores at run-time | 12:56 |
| alakx | default under settings is 1, so i figured it would use 1 thread at most, but perhaps it will detect threads and use them accordingly | 12:57 |
| alakx | btw, im talking about apache tomcat 8.5.58 and 9.0.38 | 12:57 |
| gpiccoli | ok, thanks cjwatson =) | 13:05 |
| cjwatson | The last time I used Tomcat was in 2003 :) | 13:07 |
| === ijohnson is now known as ijohnson|lunch | ||
| === ijohnson|lunch is now known as ijohnson | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!