=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
Mirvthe bot could shout and wail every time a build fails07:36
MirvI guess even smaller GCC5 updates may cause symbol changes07:38
Mirvoh, no, actually there's a reasonable explanation for this -gles build failure07:39
Mirvof course07:39
dokoMirv, where else besides destructors?07:49
=== chihchun_afk is now known as chihchun
Mirvdoko: this was me not basing on what's already in -proposed (since I've a local bzr but the -gles package is not in LP bzr), so I missed the removing of symbols _ZTV20QTextObjectInterface@Base and _ZTVN29QWindowSystemInterfacePrivate10InputEventE@Base07:59
MirvDebian has a good overview on what kind of symbols went missing from qtbase for example, in addition to those two http://anonscm.debian.org/cgit/pkg-kde/qt/qtbase.git/log/?h=experimental08:01
Mirvmostly destructors of course, but some others too08:01
morphissil2100, Mirv: can one of you upload me another android pkg to silo 48?08:11
Mirvmorphis: o/08:12
MirvI'm still laughing at this https://bugs.launchpad.net/bileto/+bug/148121508:19
ubot5Ubuntu bug 1481215 in Bileto "1000 characters is apparently insufficient." [Undecided,New]08:19
ogra_sil2100, FYI the i386 images still have the dependency issue08:23
sil2100ogra_: ok, will look into that, thanks08:25
sil2100ogra_: first I need to deal with some uninstallables in wily-proposed though08:33
ogra_sil2100, well, the emulator is broken anyway, i guess there is no hurry :)08:34
sil2100That's also what I think ;)08:34
sil2100Still, it needs to be fixed08:34
greybacksil2100: are we doing vivid+overlay only landings atm?08:59
greybackI've a dual silo which is ready to test, can the wily packages be just deleted, instead of rebuilding everything09:00
dbarthsil2100: hey; i'm trying to verify which build of oxide landed in the archive/wily; i don't have the silo on my radar anymore09:17
dbarthfrom the build logs, it still says gcc-4.909:17
dbarthso what happened to the rebuild in silo 26 yesterday?09:17
Mirvdbarth: the rebuild didn't happen. now the rebuild is there and ready, I guess sil2100 could publish it.09:28
dbarthMirv: hmm, but if i check the buildlogs, there are still mentions of gcc-4.909:35
dbarthis that expected?09:35
cjwatsondbarth: That's just updating the base chroot, which still contains gcc-4.9.  Harmless and expected.09:38
cjwatsonYou can see it installing gcc-5 as well and upgrading gcc to 4:5.2.1-3ubuntu1.09:39
dbarthah perfect, sorry for the false alarm09:43
Mirvdbarth: right.09:54
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
greybacktrainguards: are we recommended to land vivid+overlay only at the moment?10:38
Mirvgreyback: I guess the answer depends on whether you feel blocked by your package staying at wily-proposed for a little while still11:00
greybackMirv: I wouldn't, as long as I can land some code in vivid+o11:01
Mirvif it can wait there and you don't immediately have the next landing to be done (so that it'd need to merged to trunk), it's ok to have vivid to vivid+o and wily to wily-proposed until all GCC5 fixes are done. also, we can manually merge+clean the silo if the next landing is needed11:01
Mirvgreyback: so I'd personally continue doing dual landings, but sil2100 can comment on which kind of view he has11:02
Mirvof course, _testing_ on wily is also "challenging"11:03
ogra_we should just roll back to gcc-4.9 ... this transition is way to painnful :P11:03
Mirvogra_: ok, uploading new gcc-defaults!11:04
MirvGCC 2.95 was just fine11:04
cjwatson2.96 FTW!11:05
ogra_cjwatson, oh, just FYI, the checking for the PPA sources.list in config didnt work either ... in the end i decided to just rip out the whole sources.list mangling for the android package (which is fine since this livecd-rootfs is PPA only anyway)11:07
* sil2100 off to eat lunch11:49
rvrMirv: Approving silo 3012:01
Mirvrvr: thanks!12:04
Mirvsil2100: bzoltan_ just managed to remind me that we've a case of lost ubuntu-ui-toolkit from silo 013 in wily... it's not in any queue either12:05
Mirvsil2100: not Rejected, the rsync line looks correct, version number is higher than the current one. the -gles package did get in.12:06
=== alan_g is now known as alan_g|lunch
cjwatsonMirv: LP logs suggest it didn't even try to copy12:12
sil2100Mirv: I don't see it as well... I think we need to copy-package12:12
cjwatsonAFAICS anyway12:12
Mirvsil2100: yeah, I think so too but I thought it'd be interesting enough to mention. I can't copy myself so we can get eg. ogra_ to run ./copy-package --from=~ci-train-ppa-service/ubuntu/landing-013 --from-suite=wily --to=ubuntu --to-suite=wily-proposed -b ubuntu-ui-toolkit12:14
sil2100Mirv: same here, ogra_ do you have a moment for a copy-package?12:16
cjwatsonhttps://ci-train.ubuntu.com/job/ubuntu-landing-013-2-publish/68/console seems to only have published to the overlay12:17
=== chihchun_afk is now known as chihchun
sil2100cjwatson: yes, the publish to the archive should have been done by snakefruit's copy2distro, but something didn't work12:20
cjwatsonOh, right, I was misreading the publish job12:20
cjwatsonNo evidence from LP access logs that it even tried the other copyPackage12:21
cjwatsonsil2100: can I suggest that the publish job should cat the rsync packagelist to stdout in future, to make this easier to debug?12:21
cjwatsonoh, it's an artifact isn't it12:22
cjwatsonhttps://ci-train.ubuntu.com/job/ubuntu-landing-013-2-publish/68/artifact/packagelist_rsync_landing-013-wily/*view*/  so WTF really12:22
sil2100cjwatson: it's in artifacts, just look for rsync there12:22
cjwatsonyeah, just getting old12:22
sil2100It looks okayish, especially that it published its -gles counterpart from the rsync fine12:22
sil2100So copy2distro parsed it and copied the -gles one, but something went wrong with the normal UITK - we don't have any logs from what I understand12:23
cjwatsoner, with whitespace12:23
cjwatsondistro_version_at_prepare_time will have been 1.3.1549+15.10.20150710.1-0ubuntu112:23
cjwatsonbut look at https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+publishinghistory12:23
cjwatsonso it will have complained about a newer manual upload in the archive12:23
sil2100Ah, hm, but from what I remember it shouldn't have caused the copy to fail, at least I don't remember it being like that in the past12:24
cjwatsoncopy2distro fails in that case12:24
cjwatson                        'Manual upload of {} {} is newer than {}. '12:24
cjwatson                        'Not uploading {}.'.format(12:24
sil2100Damn, that script needs some love and fixing really12:25
sil2100I think we once got bitten by that before, as this really doesn't make much sense - all checks like these are done on the train side anyway12:25
cjwatsonit maybe shortens race conditions12:25
ogra_do you still need me to copy ?12:25
cjwatsonbut there probably ought to be a way to force it12:25
sil2100Let me propose a fix for that but in the meantime we need a copy anyway12:26
sil2100ogra_: yes, if you can :)12:26
cjwatsonanyway I think a forced manual copy is OK in this case, as long as it was built with gcc512:26
sil2100cjwatson: I'll double confirm, but I'm pretty sure this silo is from the times when we already landed the new gcc in -proposed12:26
sil2100ogra_: could you wait with that copy?12:27
ogra_wow, that was in the last nanosecond :)12:27
Mirvsil2100: oh fruck, I checked "ok it built on Saturday" but I looked at a wrong month.12:28
sil2100ogra_: thanks ;) Since I think it might be built with the old gcc...12:28
sil2100SInce the last build was '7 days ago'12:28
sil2100Mirv: yeah, needs a rebuild12:28
sil2100bzoltan_: ^12:28
sil2100cjwatson: thanks for the help here :)12:29
sil2100ogra_: phew, don't copy anything, we need a rebuild12:29
Mirvsil2100: I guess I could remove the vivid from the silo since it was already copied, and then they'd sync up version numbers for the next release again?12:29
* ogra_ presses n12:29
sil2100Dodged a bullet here12:30
Mirvhmm, maybe a cleaner to do a merge+clean and a more manual rebuild, to not diverge the version numbers to much12:31
sil2100cjwatson, Mirv: the good thing is that the -gles packages at least built against gcc-5 already12:38
sil2100cjwatson, Mirv: this also confused me and made me think we're ok12:38
Mirvsil2100: also since it's not in archives I can use the same version number, just via different silo12:39
Mirvthanks everyone for help12:40
=== jhodapp is now known as jhodapp|sick
pmcgowansil2100, ogra_ hey am I correct to assume the nexus 7 build should be up to date13:05
ogra_wily or vivid ? :)13:05
pmcgowanogra_, sorry vivid13:10
ogra_yeah, should be all up to date13:11
pmcgowanand thanks for fixing the android stuff13:11
ogra_yeah, turned out to take a lot more than planned :/13:11
=== alan_g|lunch is now known as alan_g
sil2100pmcgowan: yeah, all should be ok, although I still didn't find the time to fix the i386 builds13:17
bzoltan_sil2100: I see Mirv has pushed my release candidate to the silo17 where it was re-build. Is there anything I should do? Do you want a new QA round? I doubt that any functionality could be effected... but it is not my call :)14:27
bzoltan_Hmm... I see the landing branch is landed on the UITK trunk. Nice... thanks folks14:28
sil2100Oh, Mirv rebuilt it already?14:33
pstolowskisil2100, hey, may i ask for purging of ppa 41? having some weird dependency issues there...14:36
sil2100pstolowski: you want another silo assigned instead?14:36
pstolowskisil2100, whatever works for you14:37
kenvandinervr, great bug reports, thanks!14:38
rvrkenvandine: You're welcome14:38
rvrI'm finishing testing the silo14:39
kenvandinecool, thx14:39
sil2100pstolowski: ok, let me try that then14:40
sil2100pstolowski: reassigned to 2714:46
pstolowskisil2100, thanks!14:46
rvrkenvandine: Silo 32 approved14:57
kenvandinervr, thx14:57
=== chihchun is now known as chihchun_afk
sil2100kenvandine: you publish your own silos, right? :)14:59
kenvandinesil2100, already done :)14:59
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
pstolowskisil2100, hey, any idea why it failed with missing dependency https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-027/+build/7767198 when it's in the same silo: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-027 ?15:49
sil2100pstolowski: it's building?15:51
sil2100pstolowski: looks like it was a temporary build wait until the binaries got published :)15:51
sil2100(if I'm looking at the right logs)15:51
pstolowskisil2100, i've just interrupted15:52
sil2100Interrupted what?15:52
pstolowskisil2100, so i was too impatient? ;)15:52
pstolowskisil2100, interrupted the build15:52
sil2100pstolowski: ah, on the train? Yeah, probably, sometimes it might take a bit longer for the PPA to notice a dep appearing :)15:53
sil2100A watch_only build should be fine15:53
pstolowskisil2100, uh, hmm15:53
sil2100pstolowski: everything ok now?15:55
pstolowskisil2100, i'm not sure yet, started watch only build15:56
robrusil2100: pstolowski: if a package is in "Dependency wait" state, in my experience it takes about 2 hours for the PPA to automatically retry the build. it's  not something you want to hold your breath for...15:58
pstolowskisil2100, robru i see. allright, i think it's going to be fine, one of the architectures just got the dependency16:00
robrupstolowski: if you notice the dependency is published (eg it's all green and doesn't say "Pending publication" on the ppa page), we can retry the other depwait builds to speed it up16:02
* sil2100 AFK for a while16:31
rvrdobey: Silo 11 approved18:02
dobeyrvr: great, thanks18:03
veebersrobru: can you confirm for me that the autopilot release didn't get released? (due to me screwing up the qa acceptance)21:23
robruveebers: well i didn't publish it. lemme check21:23
robruveebers: right, victim of bad timing I'm afraid. alesage was making some mistakes and your change happened right around the same time. it didn't correspond with anything in the trello board so we assumed it was a mistake and set it back21:24
veebersrobru: nw, the fact that it wasn't released clears something up. I'll get that sorted today21:25
alesagerobru, veebers yep my fingers need to lose some weight21:25
veebersalesage: ^_^ lol21:25
veebersrobru: thanks for confirming21:25
robruveebers: you're welcome. I'm happy to publish it when ready21:26
veebersrobru: I might re-test it now, these issues that brendand had have made me paranoid that something has changed inbetween :-)21:26

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!