=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: trainguards | CI Train Status: #133 promoted | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [02:04] === trainguard: IMAGE 149 building (started: 20140725 02:05) === [04:44] === trainguard: IMAGE 149 DONE (finished: 20140725 04:45) === [04:45] === changelog: http://people.canonical.com/~ogra/touch-image-stats/149.changes === [05:00] shame that the new UITK did not make it to dthe 149 image [06:38] hi gentle CI train operators, can I get a silo for line 24? [06:49] sil2100, good morning [06:57] sil2100, in case you're around ↑, bear in mind we've experienced a ~new Qt crasher with this silo, we'll be investigating it asap today, but we need it to land to get the code and dbg symbols [06:57] sil2100, did someone look at the test_no_sigstop failure? Saviq ? [06:57] brendand, it's fixed in ↑ [06:57] Saviq, silo009? [06:57] brendand, yes [06:57] Saviq, which is landing when? [06:58] brendand, I just marked it OK for landing [06:58] \o/ [06:58] gonna have a green build, yeah! [06:58] brendand, there's one more known failure there, but benign and isolated to unity8 [06:58] so not really [06:58] but we just can't block this silo any longer... [06:59] Saviq, ? [06:59] Saviq, so it fixes that test, but breaks which one? [06:59] brendand, http://ci.ubuntu.com/smokeng/utopic/touch/mako/149:20140725:20140717.1/9247/unity8/1417433/ [06:59] not the "fix" fixes it, but the UI changes in the silo [06:59] s/fixes/breaks/ [07:01] :( [07:01] brendand, we want to land this silo and deal with the issues after that, dealing with them from the silo is rather painful (lack of the actual output branch and dbg symbols) [07:02] Saviq, that's unfortunate, but ok [07:02] but we'll be tackling both today, and if we can't, we'll revert the offending landing [07:03] sil2100, good morning, can I get a silo for line 24 ? [07:05] sil2100, if Saviq can get unity8 green by EOD, we buy a beer for him every day between us at the next sprint :) ? [07:16] psivaa, can you try rerunning weather app? [07:28] can I get a silo for line 23? [07:31] ;) [07:31] thostr_, oSoMoN: give me a moment [07:32] brendand: the same test has failed before. There's likely something wrong while opening the toolbar. [07:33] brendand: so yeah, give me a moment to get up-to-date on the situation [07:34] elopio, ? too much coffee :) [07:35] brendand: no, I just want not to work tomorrow and take my holiday :) [07:35] well, it's already tomorrow, I failed a little. [07:42] elopio, is there a bug? has it been investigated/reproduced locally? [07:43] brendand: not that I'm aware of. My phone is flashing. [07:46] elopio, go to bed - i'll take care of it [07:49] brendand: I'm not yet done with the performance stuff, but I'm close. [07:50] brendand: I think we will need a screenshot to understand what happened there. But that's close to land on autopilot, I wouldn't worry about it to much. [08:05] elopio, if you're still here... I need guidance... if you remember the autopilot changes on https://code.launchpad.net/~saviq/unity8/drop-filtergrid/+merge/226415 [08:06] psivaa: hmmm, why smoketesting doesn't have results for 149? [08:06] psivaa: or wait [08:06] psivaa: nevermind! ;) [08:07] sil2100: I was about to call the ambulance :) [08:08] Saviq: I'm here. [08:08] let me see your latest changes. [08:09] Saviq: ok, anyway, I'll publish unity8 now - is that crasher user visible? [08:09] bah ... silo2 failed :((( [08:09] sil2100, yeah, it is, we're working on it now [08:09] sil2100, just don't want to block stuff any longer [08:10] elopio, sorry to be bothering you, but I'm lost over here... so what it does as hopefully you'll be able to read is comparing the globalRect.y of items that are outside of the category_element (which is collapsed) [08:10] and comparing that to the height of that category_element, determining which are actually in view [08:11] brendand: after some struggle with a device, weather app is running again [08:11] sil2100: I am pleased to see this : http://ci.ubuntu.com/smokeng/utopic/touch/mako/149:20140725:20140717.1/9247/ubuntuuitoolkit/ [08:11] bzoltan: yeah ;) It's excellent, really love our dashboard now [08:12] Just a bit sad about the Unity8 blocker still present... while I don't know if I want to introduce a user-visible crash [08:12] sil2100: what is wrong with the unity8 and the weather app tests? [08:12] sil2100: ahhh, so the unit8 problem is still there... shame [08:13] Saviq: you are not bothering. But it is becoming hard to read. I'll branch to get it running, that will be clearer. [08:14] bzoltan, weather app is being investigated, but it has been floating around for a while [08:14] bzoltan, it's not always failing [08:14] brendand: I see. [08:17] elopio, actually... I think I just understood the problem [08:19] elopio, I'll deal with it, thank you for being a sounding board [08:19] Saviq: unapproved merges in the unity8 landing! [08:20] Saviq: jeje, ok. I'll finish what I'm doing and if I'm still not sleepy I'll take another look at your branch. There are a couple of things I'm not sure I like. [08:20] Is this related to the crash? [08:21] Saviq: and unity8.shell.tests.test_emulators.DashAppsEmulatorTestCase.test_get_applications_should_return_correct_applications has just passed here, btw. I though you were having problems with that one. [08:21] elopio, yeah, I was [08:22] elopio, and has it passed on your phone? in silo 9? [08:22] elopio, or just that branch [08:22] Saviq: I haven't tried the phone. Just tried that branch on my desktop. [08:23] elopio, yeah, I know what's happening, thanks [08:23] sil2100, no, that one is just a tooling change [08:24] sil2100, it's approved now [08:26] ahhh, just one failure [08:26] brendand, good news, though, I know the failure and will have a branch in a moment [08:30] free beer for Saviq! [08:30] I just published unity8, but we want to get rid of the failure and the crash! FAST :D [08:30] sil2100, bug #1348531 btw [08:30] bug 1348531 in Ubuntu CI Services "Silo branches should be public" [Undecided,New] https://launchpad.net/bugs/1348531 [08:31] and one more incoming [08:43] tvoss: google+ is crashing a lot recently we are wondering if it might be related to the webbrowser location crash, I'm going to be digging into it today :) [08:44] bug #1348535 [08:44] bug 1348535 in Ubuntu CI Services "Need -dbgsym packages from silos" [Undecided,New] https://launchpad.net/bugs/1348535 [08:45] davmor2, the webbrowser location crash should be fixed [08:46] tvoss: not according to the latest test it isn't [08:47] davmor2, where do you see that crash? do we have a bug logged? [08:48] tvoss: not yet I'm going to try some more webapps like facebook and stuff [08:48] davmor2, sure [08:50] davmor2: http://ci.ubuntu.com/smokeng/utopic/touch/mako/149:20140725:20140717.1/9247/webbrowser_app/ <- here's the crash [08:50] tvoss: ^ [08:50] tvoss: ^ [08:51] davmor2, sil2100 so the browser did not crash, but the service? [09:01] davmor2, sil2100 if so, https://bugs.launchpad.net/location-service/+bug/1347887 [09:01] Launchpad bug 1347887 in location-service "Location service should install vanilla /etc/gps.conf" [High,New] === renato is now known as Guest59000 [09:03] sil2100, line 30, can I haz silo, please? [09:08] sigh, whats that ... in silo2 the installation of procps and udev when building the chroot fails ... [09:08] tvoss: hey! Ok, cjwatson is the planned sheriff, but let me do that anyway :) [09:08] ogra_: ugh? Let me see that [09:08] https://launchpadlibrarian.net/180716223/buildlog_ubuntu-utopic-armhf.ubuntu-system-settings_0.3%2B14.10.20140725.1-0ubuntu1_CHROOTWAIT.txt.gz [09:09] sil2100, thanks [09:10] Holy moly [09:11] sil2100, ? [09:11] tvoss: it was to the thing ogra_ pointed out, no worries ;) [09:11] * tvoss is scared of silo 8 :) [09:11] ogra_: I re-ran one build to see if it was transient [09:11] ogra_: ok, it doesn't seem to be... [09:12] It failed now as well [09:12] there was one arch where mountall was the issue ... all others had procps [09:17] sil2100, brendand, got fix for both issues [09:18] hi, sorry I'm a bit late this morning === cjwatson changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard (general help): cihelp | CI Train support: cjwatson | CI Train Status: #133 promoted | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. [09:18] anything I should know from the meeting? I assume we're pushing towards another promotion ASAP ... [09:19] cjwatson, rigght, we do [09:19] there is one unity8 failure (and a few crashes) [09:19] unity8 was uploaded ... waiting for promotion to build a new image [09:20] waiting for migration to the release pocket you mean? [09:20] sil2100, I can't see unity8 in excuses, so IIUC it should migrate momentarily? [09:20] yeah [09:20] if you can't see it in excuses at all then it isn't being processed in the current run [09:21] Setting up sysv-rc (2.88dsf-41ubuntu16) ... [09:21] info: Reordering boot system, log to /var/lib/insserv/run-20140725T0903.log [09:21] success: Enabled dependency based boot system. [09:21] is that normal ? [09:21] oh, proposed-migration is stuck. will investigate [09:22] i thought we circumvented insserv [09:30] proposed-migration fixed [09:31] (my fault from changes last night, sorry about that) [09:32] I suspect everything is going to fail to build in utopic right now though [09:33] ooh? [09:33] apparently there's an apt bug that the base system just managed to tickle [09:33] so everything's falling over with "Chroot problem" [09:33] cjwatson, so it does (failing on setting up initscripts in my PPAs) [09:33] Adam's going to work on it shortly [09:33] k [09:33] But don't bother building silos in the meantime [09:34] greyback, mzanetti, bad news ↑ [09:34] well, i cant, they fail setting up the chroot :) [09:34] yep [09:34] Right, I mean don't bother trying :) [09:34] heh [09:35] well, its a good thing ... that gives us wiggle room for the new image so not to much lands [09:36] ogra_, but I *just* wanted to land a fix that would make it greeeeen! ;((((( [09:36] Saviq, oh ? i thought that was in the last upload [09:37] Saviq: is that unity8 from silo 9? [09:37] cjwatson, no, another one [09:37] cjwatson, ogra_, we wanted to land silo 9 and do a real quick apfix + crashfix landing [09:37] just after [09:38] ah, I see [09:38] well, hopefully it won't take too long to sort out [09:39] Saviq: :< [09:40] unity8 is migrating nowish [09:40] well, after p-m spends an age thinking about libav again [09:49] popey: Bill uploaded a gallery-app to the store some time ago that needs to be approved in order that we can unblock the libav transition, and it doesn't seem to be in place yet. Could you have a look please? Should be at least 2.9.1.1016. [09:49] popey, is out this week [09:49] (he pointed us to others that could do the job but i forgot who that was ... sil2100 do you remember ?) [09:50] cjwatson, ogra_: I know he pointed us to dpm and balloons [09:50] ah, dpm, right [09:50] With the exception that dpm, I think, doesn't have the power to generate click packages, but only approve them for the store or something [09:51] Ah, right, but Bill said he'd uploaded it so that shouldn't be necessary [09:51] dpm: ^- Could you have a look at that please? [09:52] cjwatson, sure, although I'll ask dholbach, as he's the one doing the reviews/approvals if popey is not there. Let me talk to him. [09:52] sil2100, cjwatson, it's about reviewing and approving gallery-app only, right? [09:59] cjwatson, sil2100, dholbach tells me that the latest gallery-app upload was already reviewed, but it was rejected because it uses the wrong framework. So someone needs to fix it and re-upload [09:59] Argh [09:59] Ouch [10:00] that was 1 day ago, with gallery-app 2.9.1.1018 [10:00] Wasn't it built by Jenkins? Does that mean Jenkins is using the wrong framework? [10:00] Or was it built manually? [10:00] no idea, oSoMoN, do you know how the gallery-app click is generally built? ^^ [10:02] tvoss, dbarth: okay so I've been opening a few webapps g+ is the only one crashing but in the log files on g+ and facebook I see a lot of libust Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:886) is this anything to do with location? Or is it an issue in webapps? [10:02] cjwatson, yes, it seems that trunk still has the deprecated framework: http://bazaar.launchpad.net/~phablet-team/gallery-app/trunk/view/head:/click/manifest.json.in [10:02] davmor2, ignore that one [10:03] ogra_: meh I'll keep digging then [10:07] dbarth, tvoss, ogra_: Sometimes I hate the phone http://paste.ubuntu.com/7854399/ [10:07] davmor2, :) [10:07] davmor2, apport-retrace works great on your host, too [10:07] lovely [10:08] tvoss: but for retrace to work you need to of viewed the file on the device first right? [10:10] davmor2, nope, just grab the .crash file, install apport-retrace, bzr branch lp:~ubuntu-archive/apport/lp-retracer-config, run sudo apport-retrace -o out.trace -S lp-retracer-config/ -C ~/retrace path_to_crash_file [10:10] davmor2, that gives you a meaningful t a a bt full in out.trace [10:10] davmor2, takes some time, though :) [10:22] tvoss: okay what am I missing? If I try a lowercase c or remove the -C altogether I get ERROR: report file does not contain one of the required fields: CoreDump DistroRelease Package ExecutablePath with the -C in place I get http://paste.ubuntu.com/7854452/ [10:23] dpm: Are core apps generally using 14.10-blah-dev3 now? [10:23] davmor2, -C ~/retracer, -C expects the cache Dir [10:23] davmor2, got the link to the .crash file? [10:23] tvoss: thanks [10:23] cjwatson, I think the community core apps are using 14.10-dev2 [10:24] we updated them all at once a few weeks ago [10:24] tvoss: http://people.canonical.com/~davmor2/_usr_bin_webapp-container.32011.crash [10:25] yes, ubuntu-sdk-14.10-dev2 [10:26] davmor2, okay, that indeed lacks a core dump [10:27] davmor2, that crash file indeed lacks a core dump [10:27] tvoss: so no use then :( [10:27] davmor2, nope [10:27] sil2100, u8 fixes are in line 32, so whenever silos are back, please expedite it [10:28] tvoss: see told you sometimes it's good to hate the phone [10:29] dpm, sorry, no, I don’t know, bfiller would know [10:29] it's like therapy [10:29] davmor2, ah okay, webapp container is a script, isn't it? [10:30] hmmm, it's not [10:30] ev, you around? [10:30] Saviq: o/ [10:30] Saviq: thanks! [10:35] sil2100, i gave up reproducing the weather-app failure [10:35] sil2100, for a little while it was really reproducible. now it's gone [10:35] brendand: maybe it was just something singular [10:35] Oh [10:35] It was? [10:35] sil2100, yeah [10:36] sil2100, next time we see it i'll file a bug [10:36] sil2100, are we pushing for our green image today? what's the outlook? [10:37] brendand, broken chroots everywhere ... we're waiting [10:38] ogra_: chroot issue is fixed. I'm retrying a mess of builds. [10:38] awesome ! [10:38] brendand: yeah, the chroot problem was standing in our way [10:38] infinity: oh, can we press rebuild now ;) ? [10:38] i thought it was waiting for another publisher run [10:38] sil2100: If by "press rebuild" you mean "retry the builds in LP", sure. If you mean "pointeless reupload", please don't. Cause I'm doing the former. [10:39] infinity: no no, just retry rebuild in LP [10:39] infinity, silo (PPA) rebuilds ... [10:39] * ogra_ tries silo 2 [10:39] ogra_: Too often when someone says "rebuild" here, they mean "re-do the whole thing". [10:39] Cause there's a button to press that makes that easy. [10:40] not in here ;) [10:40] sil2100, will unity8 pass now or does it need more landings? [10:40] brendand: it needs one more landing - now things should be better, but we need one more landing to fix a crash [10:41] dpm: or ubuntu-sdk-14.10-qml-dev2 ? [10:41] Most everything should be retrying on all arches by now. I'm just cleaning up x86. [10:41] mind you, I guess gallery-app isn't really just using the qml framework [10:42] sil2100, and is that silo created, or just in MP form at the moment? [10:42] brendand: it's in a silo :) [10:43] Saviq: ^ [10:43] * infinity looks at that suspiciously. [10:43] Saviq: no commit message for one of the merges! [10:43] sil2100, that's silo009 again i guess [10:44] sil2100: I think we can kick an image after this publisher run (has unity8 and url-dispatcher) - shall I take care of that, or do you want to wait for silo 9? [10:44] cjwatson: I would love silo 9 before that... I hope we can have it landing in the next 20-30 minutes [10:44] ok [10:45] Saviq: ! [10:45] Ok, I set a quick commit message [10:46] sil2100, oops, thanks [10:48] sil2100, i'm at hand to do anything needed to expedite things - testing, checking, rechecking etc [10:48] brendand: excellent! Saviq might be happy for some help once silo 009 finishes building [10:49] oSoMoN: https://code.launchpad.net/~cjwatson/gallery-app/framework-14.10-dev2/+merge/228273 [10:49] ARGH, FFS. [10:49] sil2100: Who did the new upload of ubuntu-system-settings just now? [10:49] sil2100: The exact thing I asked people not to do. [10:50] ogra_: ^-- That's what I was talking about. :( [10:50] infinity, err, that was me ... and i didnt do an upload [10:50] cjwatson, I believe most, if not all of them use ubuntu-sdk-14.10-dev2 [10:50] ogra_: You pushed a button that generated an upload when I just told you the build were retrying. [10:50] Pressing the "Build" button in CI Train is doing an upload. [10:50] sorry [10:50] The fact that a robot is doing it for you doesn't change that. [10:51] This is why we can't have nice things. [10:51] cjwatson, actually, either 'ubuntu-sdk-14.10-qml-dev2' or 'ubuntu-sdk-14.10-dev2' [10:51] * sil2100 didn't upload anything besides building a completely new package [10:51] dpm: I made it the latter since -qml- is kind of a lie for gallery, it uses more than just that [10:51] ok [10:53] infinity: guess we could cancel the earlier-version builds [10:53] oh, too late [10:53] sil2100, so we can build silos again/ [10:53] ? [10:54] cjwatson: Not too late to save arm64 some time, doing. [10:54] cjwatson, approved [10:54] Saviq: yes, but please do not 'rebuild' any failed builds [10:54] Saviq: those have been automatically rebuilt in PPAs by infinity [10:54] sil2100, yup ok, please recon silo 15 though [10:54] we'll need to do watch-only builds in some cases, but I'll sort that out once builders have caught up [10:55] oSoMoN: yay, thanks. I can't really test this myself - any chance you could organise a landing? [10:55] oSoMoN: in the past bfiller has wanted things merged to trunk before building a click package for upload to the store [10:56] cjwatson, that’ll be too tight as I’m leaving for the week-end in an hour from now, would you mind pinging bfiller when he comes online, he can take care of the landing himself [10:57] * infinity goes to eat his whatever-meal-this-is. [10:57] oSoMoN: ok [10:57] thanks for the help [10:57] yw [10:57] cjwatson: queues for arm64 and ppc aren't remotely pretty, if people have urgent things, you may need to go on a rescoring romp. [10:58] yeah [10:58] I'll fix PPC next week, and start costing what it'll take to fix arm64. [10:58] \o/ [10:59] ^- that's just a watch-only build [11:01] davmor2: the lltng messages are an annoyance, but they are not cause for errors [11:02] davmor2: did you manage to post the crash file somewhere to be retraced? [11:02] dbarth: no coredump [11:03] dbarth: really frustrating though, g+ just won't stay open [11:04] (6 is also watch-only) [11:04] let me try it from the browser instead [11:06] ok, that's the last couple of watch-only builds kicked off to clean up after the chroot breakage [11:07] Saviq: huh, the previous build of 6 wasn't enough then? [11:08] cjwatson, we need to build the -gles packages after the real ones go in [11:09] Saviq: ah, gotcha [11:09] looks like it hates you though [11:10] cjwatson, yeah, rightfully so [11:10] fixed by now [11:10] greyback, did you sync qtubuntu-gles, too, shall I build both? [11:10] can I get a silo for line 34? [11:10] ah too quick ;) [11:10] Saviq: yes but I kicked off a build just for it, since you had qtmir going separately [11:11] thostr_: hang on, you're in the queue [11:11] Saviq: oh qtmir-gles filed [11:11] greyback, yeah, but I broke it, will do qtmir-gles alone after it uploads [11:11] cjwatson: ack [11:11] greyback, 's fine [11:11] mandel: do you want line 12 or line 31 first? (alternatively, which will you be able to land more quickly? we're low on silos) [11:11] tvoss, dbarth: might of found a work around I crashed the webbrowser on googleplus instead :) and that is uploading to a bug report hopefully \o/ [11:12] cjwatson, let me check [11:12] * sil2100 goes for lunch [11:13] cjwatson, 12 first since it adds mms [11:13] cjwatson, 31 later [11:13] mandel: ok [11:15] cjwatson, AFAIK 12 was tested and should have a +1, let me check with sergio [11:15] thostr_: I want to keep one free for emergencies, but if you can test 4 then we can get it published which will leave you next in the queue [11:15] mandel: well, I hope so, I just assigned it :) [11:15] cjwatson: ok [11:15] barry: any progress on testing 20? [11:17] silo 16 landed at the start of the week [11:17] wut [11:17] spreadsheet must be corrupt [11:17] damnit [11:18] tvoss, dbarth, sil2100: one bug for google+ dying, https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1348592 [11:18] Error: launchpad bug 1348592 not found [11:18] logged in right on time to get the hilight; I usually don't check if I don't know about something :-) [11:18] made it public now so you should be able to get at it :) [11:18] ok, evicting 16 [11:19] cjwatson, it was tested.. I mixed line number with silo number (stupid me) [11:19] davmor2: I think that's a dup on an oxide bug [11:19] sil2100: could you sort out the spreadsheet state for line 12 when you get a minute? it should be landed [11:19] mandel: so 31 is actually still outstanding? [11:19] sergiusens: could be but I thought I would file it separate to be sure, there were a bunch of bugs that looked similar [11:20] cjwatson, 31 needs testing once 12 has been published [11:20] cjwatson, although the changes are super safe, it just updates the logging [11:20] mandel: 12 was published some time ago [11:20] mandel: as sergiusens says [11:21] cjwatson, sweet, then I'll wait a little and will test 31 [11:21] mandel: ok, I'll assign a silo for that shortly, you can't test it yet as you have to build it first :) [11:21] cjwatson: line 12? Let me take a look [11:21] cjwatson, yes, I need the silo to follow the correct path :) [11:22] cjwatson: hm, but it's being freed right now, right? So the changes haven't been merged in? Or did they? [11:22] sil2100: it's cleaning now from silo 16, but it should've been flagged as landed way before that - it actually landed on Tuesday [11:22] sil2100: so I was misled into assigning a silo for it [11:22] Oh [11:22] sil2100: didn't actually build anything in this run though [11:22] Ok, sure, let me try fixing that === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [11:26] tvoss: what are you doing there? [11:27] cjwatson, I have hit rebuild ... sorry for that [11:27] tvoss: I already sorted it out after the chroot glitch [11:27] cjwatson, oh sorry [11:28] tvoss: so let me do a second watch-only build now to get it back into the right state, unless you actually have new source changes to build? [11:28] cjwatson, nope, no actual changes [11:28] Saviq, brendand: could you guys give silo 9 a spin? It's ready [11:29] tvoss: right, done [11:29] cjwatson, thanks [11:29] mandel: building silo 16 for you [11:30] cjohnston, \o/ [11:31] sil2100, doing [11:32] alexabreu: Any luck with testing silo 11? It's been there for a while and we're low on silos [11:36] sil2100, +1 [11:37] yay, publishing [11:39] cjwatson, can you make out anything out of https://ci-train.ubuntu.com/job/landing-006-1-build/149/console ? [11:40] Saviq: that's the same problem that bit the archive proper earlier; needs a chroot update in jenkins to work around it [11:40] ! [11:40] :) [11:40] Saviq: perhaps fginther could coordinate with infinity to get that fixed [11:40] \o/ [11:40] \o\ [11:40] /o/ [11:40] (it's an apt bug, but avoidable with careful chroot updates) [11:41] cjwatson, should I just try again? [11:41] Saviq: won't help in the slightest [11:41] ugh :| [11:41] cihelp: ^- if anyone's available [11:44] bfiller: Can you make anything out of the pile of failures in https://code.launchpad.net/~cjwatson/gallery-app/framework-14.10-dev2/+merge/228273/comments/552603 ? [11:44] davmor2, some non-uploader testing of silo2 would be appreciated [11:57] ogra_: will do after Lunch [11:57] thanks !!!! [11:58] * ogra_ hugs davmor2 === alan_g is now known as alan_g|lunch [12:06] cjwatson: hey, can I get a silo for l35? [12:06] ah, remaining silos 1 [12:07] well, thats enouogh for one line, isnt it ? [12:07] :) [12:07] sergiusens: well, there's a queue [12:07] and I was hoping to keep one free for emergencies [12:08] cjwatson: yeah, my "ah. remaining silos 1" was supposed to be followed with a :-( [12:08] I'll do thostr_'s once unity8 finishes landing [12:16] sil2100, sorry, was out for a bit [12:16] sil2100, i can do that if still needed [12:16] brendand: no need, it's published! [12:16] sil2100, :) [12:16] sil2100, and we kicked a build? [12:17] Not yet, didn't migrate completely :) [12:17] But once it does, we kick a new image and do promotion dogfooding with it! [12:20] publishing that as it's not on images [12:20] cjwatson, thanks [12:24] unity8 waiting for autopkgtests now [12:24] we really need to finish landing libav so that proposed-migration can be fast again :-/ [12:25] cjwatson, what changed in libav? [12:25] out of curiosity [12:25] 9 -> 10 transition [12:25] New version, they changed the ABI [12:25] but it's ended up intertwined with a bunch of other library changes in the archive [12:26] which now all have to land at once [12:27] we have to land it before we branch for RTM or it'll be a nightmare [12:27]