[02:04] === trainguard: IMAGE 113 building (started: 20140704 02:05) === === renato_ is now known as Guest91990 [03:29] === trainguard: IMAGE 113 DONE (finished: 20140704 03:30) === [03:29] === changelog: http://people.canonical.com/~ogra/touch-image-stats/113.changes === [03:30] stgraber, ^^ so every time we archive old landing requests the the non-archived ones get shuffled around and the bot thinks they're new [03:30] stgraber, maybe needs to be indexed by the value of column A, not by the row number. or something [03:48] robru: hmm, indeed, didn't think of that === dpm_ is now known as dpm [07:28] good morning sil2100!, around? [07:31] dpm: do you need anything? maybe I can help? [07:31] morning mvo!, yes, perhaps [07:32] mvo, I'd need to retrigger a build for silo 13 after some changes I've made to the associated branch. Could you help me with that? [07:33] dpm: maybe, let me try [07:34] dpm, mvo: I'm around if anything, so just give me a sign once there are any problems [07:35] dpm: I triggered a new build now (i think) [07:35] sil2100: thanks, I reconfigured and then clicked on build and stuff is happening :) not sure if the reconfigure step was really needed? [07:36] mvo: reconfiguring is normally only required when some new branches or project have been added :) But it doesn't hurt [07:36] Normally a build would just work I guess, as it would notice changes in the branch and rebuild iirc [07:36] sil2100: great, thanks! [07:36] mvo: thanks for taking care of this! [07:36] sil2100: I will remember (or not but add to the wiki :P [07:37] mvo, sil2100 awesome, thanks! Just to be extra sure: do you guys think the last 2 comments and the change make sense? https://code.launchpad.net/~dpm/reminders-app/account-plugin-evernote-upload/+merge/225581 [07:37] dpm: hey, I'm just a mindless bot :) but I'm happy to have a look [07:37] they were required for the build in the silo to work [07:38] * dpm hugs mvo [07:41] dpm: diff looks fine in itself, you can use 0.4+bzrN too then bzr-buildpackage will pick your revno. no releated but I wonder if this could be a click? [07:44] mvo, thanks for the review! To answer the questions: I had to do this change because the ci-train choked on 0.4+bzrN (robru was surprised that it didn't work too, and suggested to do the change). I'd love this to be a click, as it would sort quite a lot of troubles that we've had, but account plugins are not yet implemented as clicks. As per the Reminders app itself, it's a click already and in the store [07:45] as far as I understood it, click installation of account plugins is still a few months away === robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #106 promoted | CI Train Sheriff: mvo, sil2100 | Known issues: The spreadsheet is extremely slow, http://bit.ly/VI2SEl knows the statuses before the spreadsheet does. [07:47] dpm: aha, ok. I was just curious, thanks! [07:48] mvo, yeah, somewhere along the way citrain lost support for version numbers not created by itself: https://ci-train.ubuntu.com/job/landing-013-1-build/59/console but I distinctly remember this being possible in the past [07:48] sil2100, ^] [07:49] oh [07:49] hey robru, so I've figured out why dh-exec failed, trying to rebuild the packages now [07:49] dpm, what was the problem? sorry I didn't dig in that [07:50] robru, the details are in the 2 last comments here: https://code.launchpad.net/~dpm/reminders-app/account-plugin-evernote-upload/+merge/225581 [07:50] robru: I think the problem might be the lack of 0ubuntu1 there actually [07:50] robru: but I'll check the code later to confirm [07:51] sil2100, thanks [07:51] dpm, ah, executable bit, curses! [07:51] indeed :) [07:59] mvo: if you could take care of the landings for some moments I would be grateful, I could finally finish up some citrain changes in peace :) [08:02] sil2100: sure [08:02] Thanks :) [08:29] stgraber, all I need from queuebot is a ping on 'trainguards' when a silo is set as testing: done and then I can finally /part #ubuntu-ci-choo-choo ;-) [08:35] brendand: meeting? :) [08:35] sil2100, yeah! === mhr3_ is now known as mhr3 [09:12] bzoltan: hi! How is the UITK landing going? :) [09:13] bzoltan: I'm asking because we're waiting for a test fix that I think is already available in your staging branch [09:13] sil2100: hello. Horrible ... failures all over [09:13] Ouch :< [09:13] sil2100: I am not sure what exactly the problem, me t1mp and kalikiana are working on it [09:15] bzoltan: thanks! It's better to notice those problems early, I guess [09:16] popey, davmor2, wow, so i just started contacts on my flo which doesnt have any contacts imported ... the app took a minute to start ... [09:17] brendand: so, it seems that this way the only promotion blocker from the ones that have reached the timeout limit is the one UITK failure that we're having, which has a fix in staging [09:17] brendand: i.e. https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1332162 [09:17] Ubuntu bug 1332162 in Ubuntu UI Toolkit "test_get_unity_top_container failed on mako#89" [Undecided,In progress] [09:17] ogra_: indeed ToyKeeper wrote a bug on that an age ago [09:17] oh, ok [09:17] ogra_: same for dialer and messaging I think though that might of changed [09:18] mvo: what other tools than strace and lsof do you think would be handy for debugging? [09:18] brendand: not sure if we can release it seperately - maybe we could whitelist it for today? As the fix is ready, and we don't want to pressure the SDK team, since it's best if they land the UITK landing well-tested [09:18] sil2100, yeah [09:19] sil2100, we'd have to talk to them about releasing it seperately. or we could just whitelist it [09:22] ogra_: als seeing slow start contacts [09:22] popey: ltrace can sometimes be useful, but its not really that important [09:23] popey: are you seeding it \o/ ? [09:23] yes [09:23] thanks, I made a note to do it but was caught in debugging something, great that you take care of it [09:23] valgrind, but it's pretty big [09:23] sil2100, they said they can do it if it's necessary (release it seperately) but prefer not to [09:23] np [09:24] sil2100: is the r112 have disabled adb? [09:24] sigh, so why does the system settings icon look like a movie projector ? ... and gallery makes me think "weather" when i see it [09:24] ogra_: what if you hit the sync button? [09:25] popey, against what should it sync ? i have nothing set up [09:25] maybe not that big, 8MB or so when you count libc6-dbg? So valgrind might possibly be worth it [09:25] ogra_: oh [09:25] cjwatson: ok [09:26] an dit is reproducable here [09:26] still takes til the display timeout to start [09:27] ogra_: is the r112 image have adb switched off? [09:27] bzoltan, nope [09:27] ogra_: ohh... in that case my device have a problem... [09:28] i only have 113 here though ... but there adb is fine [09:29] android-gadget-service status adb [09:29] bzoltan: it shouldn't have [09:29] in a terminal ^^ [09:29] ogra_: I got "error: device not found" ... reboot might help [09:29] taht should tell you if it is on or off [09:29] (terminal-app i mean) [09:29] ogra_: thanks [09:32] hi sil2100, ok, we've confirmed the packages in silo 13 to work as expected, so they should be ready for upload. Is there anything else you'd need from me to make it happen? [09:33] ogra_: when you planning on kicking next image? [09:33] popey, good question ... sil2100 ? [09:33] want one ? [09:33] not yet [09:35] bug once https://code.launchpad.net/~popey/ubuntu-seeds/add-debugging-tools/+merge/225623 merges, sure :D [09:35] ogra_: the adb is enbaled ... still no device [09:36] bzoltan, pgrep adbd [09:36] is adbd running ? [09:36] sil2100: "This source is a new package, if the destination is ubuntu, please ensure it has been preNEWed by an archive admin before publishing that stack." for https://ci-train.ubuntu.com/job/landing-013-2-publish/ - what do we do in this case? publish into the ppa is fine I assume? [09:37] mvo: publish to the PPA is fine, this is just a workaround for the fact that copies from PPA to primary archive don't currently respect NEW [09:37] ogra_: darn... it was my desktop's adb what went for a cigarette break [09:37] lol [09:37] must finish my fix for that [09:37] k :) [09:38] cjwatson: thanks [09:38] mvo: when citrain says "publish" it generally means the point when you publish the silo to the primary archive [09:39] cjwatson: ohhhh, *cough* I think I was a bit quick then :( I acked the packaging changes [09:39] and assumed the "merge&clean" would do the publishing into the real archive [09:40] mvo: Oh, no [09:40] Let me go and check quickly then [09:40] mea culpa :( [09:40] mvo: hey, yeah, this is no longer super valid - as it anyway needs to be NEWed in the archive [09:41] sil2100: it's valid until I fix the LP bug that means we don't get the opportunity to NEW-process it [09:41] copies just sail straight in [09:41] mvo: the publish step is the copy to the archive, yes [09:42] it's basically a security hole :( [09:42] sil2100: sorry, I misunderstood that [09:42] cjwatson: hmmm... for NEW packages as well? New source packages end up in the NEW queue normally [09:42] cjwatson: only new binary packages move straight to the archive [09:42] sil2100: new binaries, yes [09:42] sil2100, the bug is back :) [09:42] cjwatson: in this case it was a warning for the new source package ;) [09:42] ah, yeah, this is a new source, ok [09:42] brendand: not sure if I should be happy ;p ? [09:42] sil2100, but i have no idea why - which is sad :( [09:42] fair enough, I'll process it now [09:43] mvo: no worries :) [09:45] *puhhh* [09:45] https://wiki.ubuntu.com/citrain/NewbieGuide?action=diff&rev2=16&rev1=15 - for my future self [09:45] * mvo goes for early lunch === vrruiz_ is now known as rvr [11:10] sil2100: can I get a silo for line 15 [11:11] thostr_: looking o/ [11:11] hmmm [11:12] Let me check the conflicts [11:12] thostr_: ok, it seems that only the inforgraphics silo is conflicting, actually we can just assign a silo for you [11:13] sil2100: yes, infographic we'll tackle next week [11:13] Would be excellent, as this is another long standing silo we're having [11:14] thostr_: 004 for you [11:15] As per queuebot's info ^ ;) === MacSlow is now known as MacSlow|lunch [11:34] cihelp, anything planned for http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/ or can we use it for SDK silo testing? [11:37] Saviq, cihelp, http://q-jenkins.ubuntu-ci:8080/job/sdk-release-gatekeeper/ is already available for that purpose [11:37] thanks o/ [11:58] sil2100, could you take another look at https://code.launchpad.net/~bregma/cupstream2distro/lp-1321755/+merge/225467 I think it's really ready this time [12:03] bregma: looking ;) === alan_g is now known as alan_g|lunch [12:31] sil2100, is 113 ever going to finish? [12:31] sil2100, i think it's stuck on weather-app [12:31] psivaa-afk: are you around still? [12:31] brendand_: so, I didn't see psivaa-afk around, so we don't have anyone else that could reset/restart/kick those [12:32] And plars will be away :< [12:32] bregma: on first look it looks alright! Let me fix up what I currently have in citrain trunk and then give a spin to your branch, ok? [12:33] sil2100, sounds good === alan_g|lunch is now known as alan_g === psivaa-afk is now known as psivaa [13:02] sil2100: hey, just back..let me take a look at the results. [13:07] psivaa: yeah, so it seems UITK had some strange breakage during running and 2 test suites didn't finish yet [13:07] psivaa: seems they hanged up... [13:08] * sil2100 just hopes the devices didn't die [13:10] sil2100: with 113, i saw screen unlocking failed during weather app test and so rerunning that and online_accounts_ui [13:15] mvo: sil2100: let me check that qtc landing again [13:25] mvo: was that " fix typo in webapp app.json template" change landed without the CI before this landing? [13:26] bzoltan: yes, it was uploaded directly, but there are two(?) branches for the fix(es) [13:28] mvo: I see only this http://bazaar.launchpad.net/~zeller-benjamin/qtcreator-plugin-ubuntu/aa-clickquery/revision/191 [13:28] mvo: which one is the other...I might missed something? [13:28] zbenjamin: ^ [13:29] i just know about that one [13:29] mvo: is not that diff between the archive source package and the new source package from the silo1? [13:30] bzoltan: this one here https://code.launchpad.net/~mvo/qtcreator-plugin-ubuntu/qtcreator-plugin-ubuntu/+merge/224631 [13:30] bzoltan: and I think there was another one [13:31] mvo: hmm.. that MR is not in this landing [13:32] bzoltan: could we add it :) its broken since a couple of days and the fix is trivial [13:32] bzoltan: I'm on the phone right now, but I can look after the call if or if not its merged [13:32] mvo: sure we can [13:33] mvo: I do not think it is merged to the trunk. For that i should add that MR to the landing line on the CI Train [13:35] sil2100: how are the image tests coming? [13:36] mvo: I need to relocate now, I will be back soon from the bus. I am not sure what is wrong with that "fix typo in webapp app.desktop template". Is any of the landing MRs removing that? [13:37] davmor2: psivaa is working on those now [13:37] davmor2: how does it look like dogfooding wise? [13:37] popey: just found my mewest favourite feature. Open the camera app, click on the switch camera button [13:38] sil2100: davmor2: the image testing is now complete for 113. ubuntu-system-settings has more failures [13:38] hah, nice [13:38] sil2100, any idea why the CI train says silo 2 is building, whereas packages have been published 17 hours ago already? https://ci-train.ubuntu.com/job/landing-002-1-build/138/console [13:38] sil2100: on the whole pretty good, I might of hit the old scrolling issue on the new camera app so I'm looking into that [13:38] psivaa: oh..? [13:39] sil2100: http://ci.ubuntu.com/smokeng/utopic/touch/mako/113:20140704:20140625/8860/ubuntu_system_settings/ [13:39] oSoMoN: let me take a look, maybe there was something that broke [13:40] oSoMoN: ok, so the reason for this is that address-book-app now doesn't build for 3 architectures it was available previously [13:40] oSoMoN: i.e. arm64, powerpc and ppc64el [13:40] oSoMoN: so it's actually waiting for the dependencies of those to appear [13:41] oSoMoN: they seem to be missing the Missing build dependencies: qtdeclarative5-ubuntu-keyboard-extensions0.1 dep [13:41] oSoMoN: is this dependency mandatory? Since if it would still work without it, you could do this dep arch-dependent [13:42] sil2100, dunno, let me get renato here, he’s the addressbook guy [13:42] oSoMoN: ok :) [13:42] sil2100, oSoMoN I think this is necessary only for qml plugin and autopilot test === Guest91990 is now known as renato___ [13:43] Ah ha! renato___ was hidden here [13:43] sil2100, oSoMoN : this is mandatory for qml plugin [13:43] hmmm [13:43] renato___: so maybe the qml plugin package could be made restricted to the 3 main architectures? [13:43] renato___: since otherwise we would have to completely remove address-book-app for those 3 unsupported archs [13:43] sil2100, how this have been working until now ? [13:44] I did not change the package on this release [13:44] renato___: I have no idea, since the last version in the archive is built for those architectures - I think maybe the ubuntu-keyboard became suddenly unavailable for those 3? [13:45] * sil2100 doesn't remember if it was in the past [13:45] bzoltan1: off the phone now. qtcreator-plugin-ubuntu was uploaded (by me) a couple of days ago to fix two bugs in the templates for creating webapps. both small fixes but it was done outside of the citrain, direct dput plus merge proposals. One of the fixes is part of your landing, the other (https://code.launchpad.net/~mvo/qtcreator-plugin-ubuntu/qtcreator-plugin-ubuntu/+merge/224631) is not. so accepting this landing as it is will cause [13:45] a regression in the webapps template (bug #1327761, branch lp:~daker/qtcreator-plugin-ubuntu/fix.1327761 or my branch). I hope this makes it clearer what I wanted to says earlier :) [13:45] bug 1327761 in qtcreator-plugin-ubuntu "Creating a webapp using the default template always launche http://cookies" [Undecided,New] https://launchpad.net/bugs/1327761 [13:46] sil2100, what do you want me to do? [13:46] sil2100, how I can disable the qml plugin for these archs ? [13:46] Let me have a look at the package itself and think [13:47] * sil2100 has to check the rdeps of qtdeclarative5-ubuntu-contacts0.1 first [13:47] Ah [13:47] mvo: OK, I will add that MR to the landing silo and rebuild [13:48] bzoltan1: thanks [13:50] renato___: from what I see it might be easier than I thought, but let me double-check [13:51] fyi, I reported a bug in phablet-click-test-setup, see https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1337857 [13:51] Ubuntu bug 1337857 in phablet-tools (Ubuntu) "Cannot use phablet-click-test-setup when a newer ubuntu-ui-toolkit package was installed" [Undecided,New] [13:54] renato___: ...or maybe not [13:56] renato___: so, this might be a bit more troublesome now actually, since with this merge you added this dependency, and dialer-app and messaging-app depend on qtdeclarative5-ubuntu-contacts0.1, which now became available only for amd64 armhf i386 [13:56] renato___: it worked fine before because there was no qtdeclarative5-ubuntu-keyboard-extensions0.1 build dependency [13:57] renato___: is this dependency really needed in build time? Is it used to build things in qtdeclarative5-ubuntu-contacts0.1? [13:58] sil2100, let me check which dependency I added on this MR [13:59] sil2100, humm this was added byt elopio , because we need that to run the qml tests [13:59] renato___: hm, qml tests? Some unit tests you mean? [14:00] sil2100, maybe disable the qml tests for these arch [14:00] sil2100, yes [14:01] I guess that would make sense, we could then make this dependency 'arch-specific' if the tests are arch specific, but not sure if this would be ok from the core-dev POV [14:02] that would be fine [14:02] cjwatson, mvo: what do you guys think? ^ There is an additional b-dep added to address-book-app required by the unit tests there [14:02] Could we make the dep arch-sepecific, same with the tests? [14:02] yep [14:02] cjwatson: thanks :) [14:02] ok nice [14:02] renato___: ok, need some help with making this happen? [14:03] sil2100, let me try, I will ask you if I need some guidance, thanks [14:05] renato___: thank you :) [14:05] o/ === chrisccoulson_ is now known as chrisccoulson [14:17] sil2100: can I have a silo for line 29 please? [14:17] bfiller: hi! Let me take a look [14:17] sil2100: I know this is going to be a daft question. but why does flo have more tests that mako? I'd of thought it would be the other way around as you don't need to test phone on flo [14:17] bfiller: assigned! [14:18] sil2100: ty [14:18] davmor2: hm, I don't remember now, I guess psivaa would know best? [14:18] bfiller: hey! Shouldn't you be off today? :) [14:18] psivaa: ^ [14:18] sil2100: yes :) leaving soon [14:18] davmor2: health-check tests are not yet included in the mako results for 113 [14:18] bfiller: I hope so, don't overwork yourself o/ [14:19] sil2100: I can't help myself :) [14:19] psivaa: ah that would do it thanks :) [14:19] sil2100, I need to know which value this variable return on those archs: CMAKE_SYSTEM_PROCESSOR [14:19] davmor2: np :) [14:24] sil2100, this varible is set with the output of: uname -p [14:24] renato___: hmm, I need to find a way to get this information [14:25] cjwatson: could you help us out? Do you have any ideas how to get the uname -p values in amd64, powerpc and ppc64el platforms? [14:26] * sil2100 jumps out for a moment to drive his gf to the train station [14:26] That's the wrong way to test for the system architecture [14:26] You should be checking the userspace architecture, not the kernel processor value [14:27] Ursinha: is mako on a go slow again? This has taken an extra 3hrs (so far). http://s-jenkins.ubuntu-ci:8080/job/mir-team-mir-development-branch-autolanding/842/ [14:27] robru: for getting notification when the silo is done building and the tested flag has been set, I'll need to merge the two plugins into one so they can share information (that probably needed to happen anyway) [14:27] I'd normally suggest doing "export DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)" in debian/rules and checking $ENV{DEB_HOST_ARCH} or however you spell it in cmake [14:27] alan_g: hmm, afaik they were ok, but I can be wrong... will look [14:28] thanks [14:28] sil2100, do you have any example of debian/rules that specify which arch for the dependency? [14:29] renato___: for the dependency or for running the tests? Since for the dependencies you add the [i386 amd64 armhf] beside the dependency you want to make arch-specific in the build-deps [14:30] renato___: but that's in debian/control [14:30] sil2100, yes this is what I need [14:30] renato___: let me quickly find something before I jump out [14:30] sil2100, for running the tests I will check using that cmake variable [14:31] if you do find that you need to make parts of debian/rules conditional, then: [14:31] ifneq (,$(filter amd64 armhf i386,$(DEB_HOST_ARCH))) [14:31] [... code that is only used on amd64/armhf/i386 ...] [14:31] endif [14:32] renato___: for the deps, you can check for instance lp:unity8 [14:32] * sil2100 brb === alan_g is now known as alan_g|tea [14:37] robru, sil2100: Would it be possible to mirror the testing done and qa sign off flags from the landing tabs into the main one? That'd allow me to get everything with a single csv export rather than need to export every single tab (which would get me past the minutely quota...) === alan_g|tea is now known as alan_g [14:45] sil2100: hmmmm I think I might of just crashed lightdm [14:46] popey: is the click store available for you I get nothing? [14:47] i would tell you if my phone hadn't frozen [14:48] davmor2: works fine on my other phone [14:48] popey: yeah thanks just checked on other devices and it's fine [14:54] sil2100, can I haz a silo for line 30, please? [14:58] oSoMoN, sil2100: silo done [14:59] thanks mvo! [14:59] yw [15:01] Back o/ [15:02] stgraber: hmmm... let me think about this one, it might be possible indeed but I just hope it won't strain the spreadsheet any more than already ;) [15:03] davmor2: hm, something reproducible? [15:03] psivaa: did you re-run the UITK tests? [15:04] psivaa: since obviously it was the failure which we saw happening many times before - a singular case [15:04] brendand_: looking at the test results (while ignoring the obvious UITK hick-up), do you think we are promotion ready? [15:05] sil2100: not so far I think it might of been because for some reason the store was empty (Had to reboot to repopulate it) and I did a search which normally helps [15:06] sil2100: do you want me to re-run uitk tests? [15:06] psivaa: please :) Thanks! [15:07] uitk ? [15:07] sil2100, let me run weather and shorts test suites [15:07] what for ? [15:07] sil2100, you mean for 113? [15:07] brendand_: the latest, yes [15:07] sil2100: it has one failure which we saw in the previous images as well. i dont see the point tbh [15:07] sil2100, uitk just has one failure, known? [15:08] brendand_, olli: UITK has still 14 failures as in the morning [15:08] sil2100, nope ... wrong test [15:08] sil2100: thats system-settings [15:08] system-settings ;) [15:08] Ah [15:08] Crap... [15:08] Sorry, right ;) [15:08] Geh ;) [15:08] (thats why i asked above) [15:08] sil2100, how can I help [15:09] ogra_: sil2100 : i'll rerrun system-settings then :) [15:09] yeah [15:09] sil2100, yeah that's just a fluke. psivaa could rerun those though [15:09] psivaa: sorry! I meant system-settings ;) [15:09] ah... nevermind... the other olli/ogra [15:09] olli: ah, sorry here as well, o and tab was supposed to give ogra_ ;) [15:09] * sil2100 seems to need coffee late today [15:09] hey, I felt needed for a sec ;) [15:10] sil2100: that's alright :). running system-settings [15:11] sil2100, when do you need my ack by? i'm currently debugging the web browser issue with ricmm [15:12] brendand_: well, I would just like to know if you think we could whitelist the mediaplayer-app false-positive failure and if in overall the AP test situation looks ok for you for promotion - would like to ping ogra_ with a decision after the meeting :) [15:12] davmor2: just to make sure, so far a +1 from you, yes? [15:12] sil2100, i can give a decision in the meeting [15:13] sil2100, i don't think ogra will be there though :) [15:13] Excellent [15:13] sil2100: yeap seems okay [15:13] I know ;) [15:13] But we can ping him and get a promotion afterwards [15:13] Or in a break ;p [15:13] sil2100, half time [15:14] yeah :) [15:16] and whether he does it or not will depend on the score :) [15:17] lol [15:17] * ogra_ is prepared for the worst, no worries :) [15:17] its just a game after all [15:17] brendand_: no it will be 0-0 and come down to penalties the two teams are too evenly matched :) [15:18] davmor2, don't think 0-0 [15:18] davmor2, i'm pretty sure there will be goals [15:20] brendand_: 0-0 and 3-2 to one team on penalties that's my prediction [15:21] I don't know which team will come out on top but that is my prediction on the score [15:21] if there are penalties i'd more go for a 5-4 [15:22] but i think there will be goals during the game too [15:24] ogra_: it is rare that there are 5 penalties scored. As the pressure build and you slowly move down the players who are likely to score [15:24] ogra_: 3-2 or 4-3 is more likely [15:24] we'll see :) [15:29] davmor2, tell elopio's crew that :) [15:30] sil2100, ogra_ - 113 has my ack [15:30] brendand_: \o/ [15:30] brendand_: wait... -113?!?! [15:30] :D [15:30] hmm, even in time before the game :) [15:31] brendand_: that is 1-1 + 4-2 on penalties to give a total of 5-3 :P [15:31] Ok, so since davmor2 says +1, and brendand_ says +1 from ap side... maybe hm, ogra_ do you feel lucky enough to press the button and do a Friday-propotion ? ;) [15:31] sure [15:32] i can blame davmor2 and brendand_, right ? [15:32] :) [15:32] Yeah, I always do that! [15:32] Oh, and #blamepopey [15:32] ogra_: No you promoted it :P [15:32] oh? [15:32] sweet! [15:33] * ogra_ promotes 113 ... [15:34] ʘ‿ಠ [15:34] sil2100: packaging change in silo 1 is fine [15:34] === Image 113 Promoted === [15:34] (don't know how to record that without actually pressing the publish button) [15:34] cjwatson: oh, ok, I was wondering about this one because it's removing a version from the changelog, right? [15:35] sil2100: that's not a problem here - it incorporates the same changelog text elsewhere, and the version goes forward, so whatever [15:35] if I'd been doing it I'd have merged the full changelog entry, but just a style issue [15:35] cjwatson: ACK, ok, let me ACK the packaging and release then [15:36] Makes sense [15:38] sil2100: on the mailing list you have 3 bugs left in the blocker section right? If you are not blocking on any of those 3 why are they in the blocker section? [15:39] They're not in a blocker section, they're in the 'known issues' section ;) [15:40] This section doesn't only have blockers, but issues that affect users - which some can be made blockers if written in the description [15:40] davmor2: currently we have one blocker that we whitelisted, as the fix is pending in UITK [15:40] sil2100: which by definition is the blocker section as the other section reads * Issues not impacting user experience (will become blockers if not fixed after a while): [15:41] That comment field only means that we'll also count the timer for that, I should probably remove that already (leftover) [15:44] davmor2: thanks for pointing this out ;) === gatox is now known as gatox_lunch [15:46] Ursinha: did you find a reason for the slow CI? [15:50] sil2100: incoming [15:50] davmor2: where?! ;) [15:50] sil2100: email [15:51] davmor2: oh, hm, ok looks nice, I might change it to something similar indeed [15:52] sil2100: I'm just thinking for the sake of clarity everyone knows what is what, and how long till their bug becomes a blocker [15:53] sil2100: o/ hey [15:53] still on duty, or should i ask robru? [15:53] dbarth: what's up? :) [15:53] can i haz a silo again for line 21? [15:53] Let me take a look [15:54] we've fixed the branches [15:54] dbarth: oh, is it ready? Since it wasn't set as ready [15:54] alan_g: sorry taking this long, we don't have many people around today [15:54] dbarth: let me assign a silo then :) [15:54] it is now, let me toggle the flag [15:56] Ursinha: I understand. I'm just keeping track of how CI can be so slow (it isn't blocking anything yet). [15:57] dbarth: ah! It seems that I can't assign a silo now :( oSoMoN got a silo for webbrowser-app today already [15:58] ah right, he did [15:58] i let him pass, cause our tests were still not good [15:58] hmm, ok, i'll see with him [15:59] dbarth: thanks! And sorry for that :) [15:59] alan_g: alright, thanks for letting us know [16:02] dbarth, sil2100: my silo is about to land, after which you’ll be able to get one [16:06] oSoMoN: ah ok, cool [16:06] i'll take a look after the first half time :p [16:13] dbarth, oSoMoN: robru is around now so he'll be your train driver ;) [16:14] robru: btw. I noticed it has to be depressing to live in the US timezone! [16:14] robru: when you actually start your day, we're actually already finishing up and making you feel depressed about having to still work for the whole day ;) [16:14] Sorry about that! [16:15] sil2100, ahhhh, but the best part about waking up so late is that after noon, everybody's signed off and there's nothing to do anyway ;-) === sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #113 promoted | CI Train Sheriff: trainguards | Known issues: The spreadsheet is extremely slow, http://bit.ly/VI2SEl knows the statuses before the spreadsheet does. [16:15] sil2100, but when you start your day, robru is fast asleep, or away partying :) [16:15] hah! [16:15] ;) === robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #113 promoted | CI Train Sheriff: robru | Known issues: The spreadsheet is extremely slow, http://bit.ly/VI2SEl knows the statuses before the spreadsheet does. [16:16] davmor2, 12 mins gone and you're already wrong :P [16:17]