| ESphynx | hey guys, why would a build fail, with no build log? | 07:21 |
|---|---|---|
| geser | ESphynx: most probably LP lost track of the build, try a "retry" of it | 07:22 |
| ESphynx | geser: It happened on 2 builds though ( at same time ) | 07:23 |
| ESphynx | I clicked retry on both | 07:24 |
| jfi | same issue with my package few minutes ago, a build has failed without any log | 07:37 |
| wgrant | jfi, ESphynx: Which builds? | 07:40 |
| jfi | wgrant, https://launchpad.net/~jfi/+archive/psensor-unstable/+build/4406549 , I have "retried" it, so you can no more see the message | 07:42 |
| wgrant | jfi: Thanks. | 07:43 |
| wgrant | Looks like we have three builders that are a bit unhappy and breaking things. | 07:43 |
| wgrant | I've disabled them for now, so that should stop happening. | 07:43 |
| jfi | ok, thanks wgrant for the quick solving:) | 07:43 |
| wgrant | Thanks for letting us know. | 07:44 |
| wgrant | (if a build fails to start repeatedly, we try to work out if it's the builder or the build that's causing the problem... in this case I can see was the builder, but the automatic check erroneously decided it was the build instead, so it got failed to get it out of the queue) | 07:45 |
| teolemon | as for thanking, thanks wgrant for the LP translations fix :-) | 07:52 |
| wgrant | teolemon: Due to the long weekend it won't be fixed on production until the middle of next week, but I've confirmed that all the missing strings show up with the new code. | 07:54 |
| jfi | wgrant, hum, failed again, same message, you can see it at: https://launchpad.net/~jfi/+archive/psensor-unstable/+build/4406549 | 07:54 |
| jfi | wgrant, this time I have monitored to see which build it is: https://launchpad.net/builders/chindi02 | 07:54 |
| wgrant | Maybe some more builders have joined the party... | 07:54 |
| wgrant | Ah, no, that's just fallout from the previous failure. | 07:55 |
| jfi | I am going to do a test the build on my computer with pbuilder, maybe that's my fault | 07:55 |
| wgrant | Retrying doesn't reset the failure count | 07:55 |
| wgrant | It's not your fault | 07:55 |
| wgrant | But once a build gets killed once due to several successive failures, a single failure will cause it to be killed. | 07:55 |
| wgrant | Retrying it again will hopefully work | 07:55 |
| wgrant | If not, I will find a bigger hammer. | 07:56 |
| jfi | ok, I hit retry again | 07:56 |
| jfi | hum the build score is strange, it has been changed to Build score:99999, never had this kind of value | 07:58 |
| wgrant | That's because I want to make this work :) | 07:59 |
| wgrant | It should be working now | 07:59 |
| wgrant | It has a log | 07:59 |
| jfi | yes, sounds good, started on chindi01 , instead of chindi02 previously | 08:01 |
| jfi | "Finished a moment ago (took 3 minutes, 48.0 seconds) " | 08:02 |
| wgrant | Great | 08:03 |
| wgrant | I'm fixing the retry code to reset the failure count, so a bad builder won't carry over after a retry. | 08:04 |
| === Nigel_ is now known as G | ||
| shadeslayer | hi, is the upload processing kaput? | 11:07 |
| shadeslayer | I uploaded a package quite some time ago, no emails so far | 11:08 |
| czajkowski | shadeslayer: hmm not seen any issues | 11:08 |
| czajkowski | wgrant: something changed? | 11:08 |
| shadeslayer | hm, I guess maybe it didn't upload from my end then | 11:09 |
| crass | I've deleted some packages in a PPA, but the binary Mb usage has not gone down. One it reaches the max of 2gb, will it delete the oldest binaries? | 11:09 |
| shadeslayer | crass: it'll delete the binaries whenever on the next cleaning run | 11:10 |
| shadeslayer | it takes time for the binaries to go away afaik | 11:10 |
| crass | ok, thanks | 11:10 |
| * shadeslayer uploads again to make sure | 11:10 | |
| crass | why is this import stuck on "updating branch.."? https://code.launchpad.net/~vcs-imports/grub/grub2-bzr | 11:13 |
| crass | the location appears to be correct | 11:13 |
| voldyman | guys i want to fetch all bugs realted to a project but the API doesn't provide something like that, any better way than scraping the site? | 11:15 |
| shadeslayer | czajkowski: I think my earlier upload didn't quite get uploaded | 11:16 |
| geser | voldyman: doesn't the "searchTasks" method of a project object doesn't work for you? | 11:20 |
| === Mission-Critical is now known as MissionCritical | ||
| === benji___ is now known as benji | ||
| === teknico is now known as teknico_away | ||
| shadeslayer | czajkowski: not sure if you're aware of the issue or not but https://launchpad.net/builders/ is inaccessible for me | 12:58 |
| czajkowski | shadeslayer: yup thats normal ;) stuff being built that people don't need to see | 12:59 |
| czajkowski | it'll be fine in a bit | 12:59 |
| shadeslayer | ah | 12:59 |
| shadeslayer | :D | 12:59 |
| shadeslayer | czajkowski: but then won't that be visible in the build history of a builder? | 13:01 |
| czajkowski | it'll be finshed son shadeslayer | 13:04 |
| czajkowski | *soon | 13:05 |
| === wedgwood_away is now known as wedgwood | ||
| === jamestunnicliff_ is now known as jamestunnicliffe | ||
| dobey | i really wish that bug would get fixed | 14:43 |
| czajkowski | it's marked as high as soon as we finish the last 100 criticals I'm sure they;ll get right on it :) | 14:44 |
| wgrant | dobey: We have a lot of bugs, many of which prevent users from doing things, and not very many engineers | 14:51 |
| wgrant | That bug doesn't break any significant Launchpad functionality | 14:51 |
| wgrant | So it's not terribly high priority. | 14:51 |
| wgrant | We are, of course, happy to help people fix bugs like that. | 14:53 |
| wgrant | Or any bugs :) | 14:53 |
| czajkowski | pick a number any number | 14:53 |
| wgrant | But we don't have the resources to fix everything today :) | 14:53 |
| dobey | right. it's just distracting when it keeps coming up and people ask about it :) | 14:53 |
| czajkowski | dobey: oh indeed, every week I get asked | 14:53 |
| czajkowski | today it appeared on -devel | 14:53 |
| dobey | yeah | 14:54 |
| czajkowski | but at the end of the day it's not breaking lp, :/ | 14:54 |
| czajkowski | have to draw the line somewhere | 14:54 |
| czajkowski | I relaly should eat llunch at some point today | 14:54 |
| davmor2 | czajkowski: 1 | 15:33 |
| czajkowski | if you cna fixt bug 1 :)have fun | 15:34 |
| ubot5 | bug 1 in Ubuntu "Microsoft has a majority market share" [Critical,In progress] https://launchpad.net/bugs/1 | 15:34 |
| === Kyle_ is now known as Kyle | ||
| === vednis_ is now known as mars | ||
| === matsubara_ is now known as matsubara | ||
| === Ursinha-afk is now known as Ursula | ||
| george_e | This is probably a strange question but... how do I delete ARM builds from my PPA? | 22:03 |
| george_e | One of the packages in the PPA provides ARM builds but since that package is used as a dependency of another package that does NOT provide ARM builds, it's just wasting space. | 22:03 |
| czajkowski | george_e: what ppa ? | 22:04 |
| george_e | czajkowski: https://code.launchpad.net/~george-edison55/+archive/nitroshare-dev/+packages | 22:04 |
| czajkowski | ARM isnt enabled on the nitroshare-dev ppa | 22:04 |
| george_e | That's correct - I copied the binaries from another PPA. | 22:05 |
| george_e | I only wanted to copy the amd64 / i686 binaries, but the ARM ones were copied as well. | 22:05 |
| george_e | There didn't seem to be an option to exclude any architectures. | 22:05 |
| === wedgwood is now known as wedgwood_away | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!