[00:00] Woot, been waiting for that. [00:01] ToyKeeper, ahh you're welcome [00:02] Oh, but this doesn't have a new mir? [00:02] D'oh. I was mostly waiting for a new mir to test. :) [00:02] ToyKeeper, nope, this is specifically a big pile of changes before I land new mir ;-) [00:02] Okay. r244 has had quite a few graphical issues which might be resolved by a mir update. [00:03] ToyKeeper, yep, kgunn gave the green light on the mir update, I'm testing it myself right now, I just don't like any single image to have too updates because then it gets harder to bisect which change caused a problem. [00:04] ToyKeeper, if you really are impatient, enable silo 18 and make sure the fixes really fix things ;-) [00:14] robru, I think silo 11 is ready for publishing; feel free to test it if you want https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc&usp=drive_web#gid=29 [00:15] sergiusens, thanks. how would I test that? [00:16] robru, so it just exposes something extra for ocide; oxide is not there yet; so just running the autopilots we have and making sure display isn't broken is enough [00:17] sergiusens, ah ok. great. will publish it shortly (just testing mir now) [00:21] robru: please let me know when the silo is ready [00:22] boiko, oops, forgot to ping you. did that way back when I said i was doing it ;-) [00:23] robru: nice! thanks! I will build the packages to start testing again tomorrow [00:23] boiko, great [00:25] and with that I call it a day, see you! [00:51] doanac`: got a second? [00:54] veebers: doanac`: It doesn't look like the PPA is being added, the same issue we had with the gatekeeper job a while ago: http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/81/label=mako-07/console [00:54] if you search the console log for 'ci-train-ppa-service/landing-003' [00:54] I can't see the PPA ever being added [00:54] but perhaps one of you gents can see what I've missed [00:55] thomi: ugh :-\ perhaps the recent changes mean those details are echoed to log? (not sure, that's a long shot) [00:55] * veebers looks [00:55] I also couldn't see where the python-autopilot package was installed, which would allow us to compare the version numbers [00:56] thomi: I can see the ppa being added to "phablet-config writable-image" which wasn't happening last time (hence the change to specific revno) [00:57] veebers: right, I see that as well, but I don't think it's doing anything [00:58] thomi: I see similar output for phablet-config in the previous run (i.e. the version that worked) [00:59] hmmm [00:59] the previous version had plars' workaround [01:00] thomi: this run also has plars' work around, just updated code too. Doesn't searching for "Autopilot Package Version" give you the version? [01:00] Autopilot Package Version: 1.4+14.04.20140318-0ubuntu1 [01:00] veebers: hmmm, ok [01:01] maybe it is working [01:09] === trainguard: IMAGE 245 DONE (finished: 20140319-01:10) === [01:12] woooot [01:12] PUBLISH ALL THE THINGS! ;-) [01:14] ToyKeeper, just published mir. next image build will be kicked by cron in about an hour [01:22] :) [01:40] sergiusens, still around? [01:40] robru, was closing, anything urgent? [01:40] or that I need to look into? [01:41] sergiusens, oh i was just wondering about silo 10, just happened to notice that the packages are from over a week ago. [01:42] sergiusens, and it's the only silo that has packages older than a day ;-) [01:42] robru, oh, that's waiting for a gallery fix [01:42] robru, don't want to destroy it yet as it takes time to setup [01:42] sergiusens, ok. we're down to 15 silos active, so I guess I don't need to jettison it after all, but I was kind of thinking "I wonder if I can jettison the oldest silo..." [01:42] sergiusens, ok no worries [01:42] and it has the goodies the qa and ci team want [01:43] ;-) [01:43] sergiusens, good night! [01:44] good night! [01:44] well, not night for you just yet :-P [01:44] enjoy [02:53] * ToyKeeper wonders if that image is still happening any-minute-now, or if she should call r245 "it" for today [02:55] ToyKeeper, should be starting within the next half hour as far as I know, but it does take 1hr usually to build them. [02:57] I can at least confirm that r245 didn't fix the mir screen update issues. [02:58] ToyKeeper, no worries, wasn't expected to [02:58] ToyKeeper, 246 is for you. mir is fully published and even the silo is cleaned, there's no way that image 246 can be kicked without it [02:59] No worries... got a meeting now, and I'll check afterward. :) [03:04] robru, silo landing-017 tested and ready for you to hit publish [03:04] bregma, thanks, I might wait a couple hours on that. unity and mir in the same image would probably give didrocks a heart attack ;-) [03:05] no wait [03:05] unity7 ;-) [03:05] * robru has phones on the brain [03:05] it's the good kind [03:05] bregma, ok, publishing [03:05] sweet, I might get to bed tonight after all [03:06] * bregma needs to adopt better work hygeine [03:06] bregma, don't we all? ;-) [03:06] bregma, ok, you are published. [03:06] bregma, it's only 8PM for me, if you want to get some sleep I can merge & clean later [03:07] robru, sure, if you're not busy I'd appreciate it [03:07] bregma, no worries [03:21] thomi: looking at the job. i see this line: INFO:run-smoke:Running: /var/lib/jenkins/slaves/mako-07/workspace/autopilot-release-gatekeeper/label/mako-07/touch/scripts/provision.sh -i touch -p python-autopilot -p autopilot-touch -p libautopilot-qt -p libautopilot-gtk -p python-gi -p ubuntu-ui-toolkit-autopilot -p friends-app-autopilot -p mediaplayer-app-autopilot -p gallery-app-autopilot -p webbrowser-app-autopilot -p camera-app-a [03:21] utopilot -p dialer-app-autopilot -p messaging-app-autopilot -p address-book-app-autopilot -p ubuntu-system-settings-online-accounts-autopilot -P ppa:ci-train-ppa-service/landing-003 [03:22] the -P ppa:.... indicates it gets added [03:22] doanac`: OK, I expected to see the output of add-apt-repository somewhere [03:22] doanac`: also, didn't it use to show when packages were installed? [03:22] thomi: i think that happens in the "phablet-config" command. it probably just swallows that output unless it fails [03:22] as in, the output of 'apt-get dist-upgrade' ? [03:22] ahhh [03:22] OK [03:23] would it be difficult to add that? [03:23] thomi: probably not. let me take a quick look at phablet-config [03:26] doanac`: It's not urgent, it looks like it's doing the correct thing, but it'd be nice to see the output of add-apt-repository and apt-get dist-upgrade [03:26] would make it much easier to confirm that it's working correctly [03:26] thomi: i just jumped on the phone and confirmed apt had it configured [03:26] cool [03:26] as per getting the output. i'm sure its easy to patch phablet-tools. to show the output. [03:26] we ended up comparing the version numbers [03:27] that would be awesome [03:28] thomi: actually its a little annoying fixing it in phablet-tools based on my reading. not hard, but not trivial [03:28] it might be easier to dump out that kind of information in that hook you use in your job [03:28] doanac`: ok, well, it's OK as it is I suppose :) [03:30] * doanac` goes to bed [03:32] robru, I'm still around so I'm doing my own merge & clean, but thanks for the offer [03:32] bregma, oh ok, cool. [04:09] === trainguard: IMAGE 246 building (started: 20140319-04:10) === [04:11] ToyKeeper, ^^ seems I mis-judged the time of the build by an hour, I guess some DST has thrown it off or something. Anyway it takes an hour to build so if you're still around an hour from now... [04:12] Yeah, I don't normally attempt sleep for at least another 4 hours. :) [04:13] excellent [04:13] no, sorry, my fault [04:13] had to disable cron as we built an image just a few hours ago [04:13] and wanted to make sure my livecdrootfs changes were good for next image [04:13] rsalveti, ahhh, ok [04:13] sorry delaying it for 1 hour [04:14] I have *plenty* of other things to work on... I'm not blocked at all. [04:14] same, no worries [04:16] ... like a huge pile of tickets, or adding video encoding to my mirscreencast wrapper, or finishing a little UPay app to help with purchase support. [05:19] === trainguard: IMAGE 246 DONE (finished: 20140319-05:20) === [05:20] ToyKeeper, ^^^ ;-) [05:24] hmm [05:28] nice that "DONE" means "your device will update to it" too immediately [06:23] morning! [06:43] flashy flashy [07:11] didrocks: You're just in time. Image 246 landed and seems to fix the graphic freezes which plagued r244 and r245. [07:11] ToyKeeper: excellent news \o/ [07:12] ToyKeeper: nothing worrying in the dogfooding side in 246? [07:12] cihelp: no mako available though [07:12] Not yet, but I just started. [07:12] ToyKeeper: great! thanks for the good news in the morning :) [07:12] (was waiting all day for a testable image) [07:13] subprocess.CalledProcessError: Command '['bzr', 'checkout', '--lightweight', u'lp:ubuntu-calendar-app', '-r', u'201', 'work']' returned non-zero exit status 3 [07:13] humn, seems bzr didn't like [07:13] let me try to restart mako [07:14] * didrocks wonders why some security tests failed [07:22] Hmm, that's odd. My mako seems to have drained its battery even though it was plugged in. [07:26] ToyKeeper: are you sure it was charging? Sometimes, the mako software (it's software) to charge can have races [07:27] Not sure. I left it idle for a day or so, and found it so dead it couldn't even display the firmware's charging screen. [07:27] yeah, was probably not "plugged" for the firmware's charging process [07:28] I've noticed, during use, that it can still decrease the overall charge level even while charging. [07:29] ... but then again, this unit was somewhat abused in a past life. It was jfunk's, and I think he made a habit out of letting the battery drain completely. [07:29] Definitely not good for Li-Ion cells. [07:32] right [08:06] so, what about the test results this time for the newest images? [08:06] I've been polling the new url [08:07] I'd ping ci_help but I assume there won't be anyone around before the first vanguard wakes up [08:08] didrocks: the sdk test should be fixed now btw [08:08] Mirv: I've restarted the tests on the newest images [08:08] as it was stuck [08:08] seeing the sdk test passing, great! [08:09] Mirv: the security ones are failing though, mind having a look? [08:09] Mirv: and see if anything changed/entered the archive? [08:10] good morning [08:10] could i have a silo for line 13? [08:11] (we landed silo 6 yesterday) [08:11] those are quick bug fixes for the html5 sdk [08:11] dbarth: looking [08:11] sil2100: thanks [08:12] didrocks: ok, great. aha, looking. [08:16] didrocks: do I see correctly on the mir no-screen-refresh bug that it's fixed and released on 246? \o/ === vila changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: vila | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: none [08:17] sil2100: yeah, seems so! :) [08:17] sil2100: there is only the unity-mir issue remaining, right? [08:29] didrocks: hi, i understand that our unity-chromium-extension got stuck in proposed yesterday [08:30] didrocks: do i need to pass a branch for that, or did robru unblock that already? [08:31] oh.. so the results are back at the old place [08:33] hmm, http://people.canonical.com/~ogra/touch-image-stats/20140318.2.changes (#245) [08:36] dbarth: I do see it in the release pocket [08:36] dbarth: so, all good :) [08:36] dbarth: it's in release pocket, so I guess it's ok ;) [08:38] so who in addition to jdstrand but perhaps closed to our timezones could understand what's going on in the security tests? a lot failures, but I fail to think of an update that could have caused it [08:38] closer [08:38] I also checked the tests themselves that they don't seem to have changed [08:40] Mirv: did you try running them locally? I usually waited for jdstrand, not sure who else could take a look [08:41] didrocks: ah cool;thanks [08:41] and thanks for the silo [08:41] yw :) [08:41] would be nice to do our first investigatoin [08:41] as his code didn't change apparently from Mirv's link [08:42] Mirv, didrocks: but on the previous image it was also failing [08:43] Ah, no change [08:43] Nevermind then [08:48] sil2100: trying to... === Ursinha is now known as Ursinha-afk [09:05] hum, why is landing-007 stating "building" when the ppa is done building since yesterday evening [09:05] oh, hey there btw ;-) [09:08] ehm, why can't i get anything from system-image.ubuntu.com? [09:08] Hey [09:09] seb128: looking [09:09] sil2100, hey, thanks [09:11] seb128: interesting - it seems citrain did not register any 'build' operation for the current silo, I wonder how the package appeared in the PPA [09:13] seb128: not really sure what happened, but I guess we can simply fix it by re-running build - maybe even with watch-only [09:13] jenkins went down [09:14] tonight [09:14] so it can be while this was running [09:14] Ah, makes sense [09:14] and jenkins forgot about the job once restarted [09:14] (but dput could have already been proceeded) === Ursinha-afk is now known as Ursinha [09:15] sil2100, didrocks: can you do whatever you think is right to it? [09:15] e.g trigger a rebuild, or watch only rebuild, or...? [09:16] I thought sil2100 was going to relaunch with watch only [09:16] Will do that, thought the lander will do it ;) But I will [09:17] I can reproduce at least the ./click-apparmor 2 failures [09:17] seb128: all is cool now [09:17] sil2100, well, cjwatson started those build and I'm not sure if he's around yet, so we can as well keep things moving meanwhile [09:17] sil2100, thanks [09:18] Mirv: if the code doesn't make sense to you, you can probably bisect the component that were upgraded [09:18] Mirv: :< [09:18] as we know at which image it started from [09:19] yes, the list is just quite.. interesting http://people.canonical.com/~ogra/touch-image-stats/20140318.2.changes [09:19] I wouldn't be surprised to find that downgrading doesn't help, but we'll see [09:21] hmm, although I have "start: command not found" [09:22] Mirv: but you can reproduce locally, right? [09:23] Checking aa-exec-click ... !FAIL! [09:24] I would start with that [09:24] ToyKeeper, did you push your pictures via mtp ? [09:24] (it should run as the phablet user) [09:26] didrocks: no, I thought I could since I had the same number of failures. but I had aa-exec-click passing while two "Checking application upstart job":s failing [09:26] ogra_: No, I just 'adb push'ed them as a tarball, then unpacked. What's weird is that the script did a chown phablet.phablet on all the files afterward (and the dir itself ended up with the wrong owner somehow). [09:26] aha [09:26] I'm seeing now how apparmor-easyprof-ubuntu while preparing to downgrade packages [09:26] Mirv: yeah, the infrastructure could have changed as well maybe [09:26] ToyKeeper, well, for adb thats the right owner since we run it as a root shell by default :) [09:27] you need to take extra steps when using is [09:27] *it [09:27] It wasn't root.root though, and it actually changed back to system.system a few times after I manually chown'd it to phablet. [09:27] yes, adb is evil :) [09:28] it also removes all executable bits from files (in case you copy some binaries in the future, you need to make them executable again) [09:28] Hmm, I haven't found that to be the case. [09:28] or "official" way of tranferring data is mtp [09:29] I routinely 'adb push mirshot.py /home/phablet' and it's still executable afterward. [09:29] intresting [09:29] i always end up with non executable binaries when i do that [09:29] It's root.root, as expected, but it's mode 777. [09:30] bug 1204925 [09:30] bug 1204925 in android-tools (Ubuntu) "adb/adbd should not unset executable bits " [Undecided,New] https://launchpad.net/bugs/1204925 [09:30] ogra_: sil2100: didrocks: do you know who to go to with Jenkins autobuild issues? I see that MRs from outside of the team are not triggering Jenkins build. [09:30] hmm, might only be the case when you pull from the device [09:30] What I found particularly odd was that Gallery refused to show anything, even though the dir and all its contents were readable. [09:30] bzoltan, see backlog [09:30] bzoltan, jenkins outage [09:30] bzoltan: it's the CI team [09:31] ogra_: he's talking about another jenkins [09:31] oh ok [09:31] ETOOMANYJENKINS [09:31] :P [09:31] +1 :p [09:31] didrocks, bah, still no HO link ... the location hasnt worked either [09:32] ogra_: yeah, see! :p [09:32] i though it was a clever hack :P [09:33] didrocks: sil2100: just a quick update for the meeting - so far no failures in apparmor-easyprof-ubuntu, even though 118 failures on test infrastructure including right in the beginning. it's still running. [09:34] I'm glad to see some libc error code humor. I have a bad habit of proclaiming "ENOENT!" when I look for something and can't find it. [09:35] People get the joke a lot more often if phrased using a different standard though... "404 pizza not found" [09:35] haha [09:48] sil2100,seb128: right, jenkins was waiting for 007 to build when it crashed [09:48] thanks for poking that [09:49] cjwatson, yw! [09:49] cjwatson: np :) [09:50] publishing that since seb128 tested it last night [09:50] confirmed, works fine on my n4 [09:51] o/ [09:54] popey: search on music lens is it crashing for you still? [09:54] "still"? [09:54] implying it always did? [09:55] popey: I'm seeing it now but I thought you had seen it before [09:55] nope [09:55] never tried it, ever [09:55] but yes, i get a unity8 crash when searching in the dash [09:55] s/dash/music/ [09:56] hey, the desktop boot speed tests seem to be totally bogus because of blocking waits on utah-done.py, see https://jenkins.qa.ubuntu.com/job/bootspeed-trusty-desktop-amd64-acer-veriton-01/98/artifact/11/bootchart.png - can somebody fix this? [09:57] nuclearbob, ^^ [09:59] i would have reported this earlier, but the graphs have been broken for *months* [09:59] cking, that looks like something logging in every 5s and consuming like 2-3 seconds of cpu each time, winner [09:59] something very utah and very wrong then [10:02] guys, who do i have to bribe so we get timestamps in the logs of https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-trusty/1420/consoleFull like the ones at http://build.kde.org/job/kde-runtime_oldstable/7/consoleFull ? [10:03] perhaps I'll file an issue report in asana too [10:04] psivaa: sil2100: so just FYI I ran apparmor-easyprof-ubuntu manually on #246 and had 0 failures where as http://ci.ubuntu.com/smokeng/trusty/touch/mako/246:20140319.2:20140304/7259/security/ shows 118 failures... [10:04] tsdgeos, you have to bribe the CI team to install the timestamper plugin in jenkins [10:05] Passed: 1381/1381 [10:05] jibel: and who would be in that team? [10:06] Mirv: ok, could be something ci specific. i'm going through the logs now there [10:06] vila, ^^ see tsdgeos request for you [10:12] tsdgeos: rather than adding a plugin (which has issues), can you use annotate_output for that job ? [10:13] vila: what is annotate_output? [10:14] tsdgeos: sorry, annotate-output: annotate program output with time and stream [10:14] vila: still no idea of what you're suggesting :) what is "annotate-output"? an option of the job? [10:14] tsdgeos: it's part of the devscripts package so probably available everywhere you need it [10:15] vila: ah you mean running my program with annotate-output? [10:15] tsdgeos: yes [10:15] vila: what's the issues the plugin has? [10:16] tsdgeos: not that on in particular, we have issues maintaining plugins with jenkins in general [10:16] s/on/one/ [10:16] ok [10:16] tsdgeos: so we try to limit their use and preferably not add new ones while we try to get rid of them ;) [10:22] didrocks, FYI http://people.canonical.com/~ogra/touch-image-stats/246.changes .... the bot should now set changelog links after the build is done (and announce them here with the "DONE" message) so we dont need to dig through cdimage build ids anymore [10:23] ogra_: great! [10:26] OK, so what drugs exactly is qmake on? [10:26] https://launchpadlibrarian.net/169947029/buildlog_ubuntu-trusty-ppc64el.ubuntu-download-manager_0.3%2B14.04.20140317-0ubuntu1_FAILEDTOBUILD.txt.gz [10:27] search for arm-linux-gnueabihf, and notice the architecture [10:27] Mirv: ^- [10:28] fun fun [10:29] I'm sure on non-prescribed ones [10:31] no mention of arm-linux-gnueabihf in the qtbase build log [10:31] Multiple images were produced: [10:31] #241: [10:31] - got the unity8 locking screen/hud removal revert fix in. [10:31] what does "hud removal" mean? [10:32] Saviq: ^ [10:33] Saviq: ping, I'm looking at bug #1294233 but it seems I can't reproduce ? O_o [10:33] bug 1294233 in Ubuntu CI Services "Unity7 shortcut hint needs to be closed in otto testrunners" [Undecided,New] https://launchpad.net/bugs/1294233 [10:33] Wellark, we're dropping it from the bottom edge, pending design for a new place for it [10:34] vila, maybe someone touched the file I mentioned already? [10:34] Saviq: is there a bug to track that pending design? [10:34] Wellark, not that I know of [10:34] Mirv: oh, sorry, this isn't qmake's fault really, ubuntu-download-manager has a crazy .pri [10:34] Saviq: well, no, I'm supposed to do that ;) So I was wondering if a different fix was applied... [10:34] Saviq: well, how do we track it then and get designers to work on it? [10:35] Wellark, they are being gotten to work on it without our intervention [10:35] Saviq: who is working on that? [10:36] Wellark, bearing in mind our limited design resources it's probably on the backlog [10:37] Saviq: so no way of invoking the hud anymore and no ETA on when we get it back then [10:37] Wellark, yes [10:37] well, given the amount of time me, ted, pete and marcus have put into that I find the situation unfortunate [10:37] vila, not that I know of, https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/3533/ is the last unstable job ran [10:37] vila, and it still has the overlay on [10:38] Saviq: http://s-jenkins.ubuntu-ci:8080/job/autopilot-testrunner-otto-trusty/3541/ [10:38] and no bug to track the progress of design [10:38] I will file one then. [10:38] cjwatson: ok, that's at least good news. I was thinking that even with our large CMake usage we probably must have had succeeded qmake builds too. [10:38] vila, oh well, yeah, I said on the bug that I can't confirm that's actually affecting the results [10:38] hmm, where did sil2100 go [10:38] vila, but still needs to go to not mess with the video output [10:39] Mirv: http://bazaar.launchpad.net/~ubuntuone-hackers/ubuntu-download-manager/trunk/view/head:/common-project-config.pri [10:39] Saviq: oh, "might" [10:39] Mirv: you may be ill now [10:39] vila, you need a failing test to get the video :) [10:39] Saviq: ack, so it may not be reproducible and still need to be fixed, ack, too bad it can't be reproduced reliably then :-/ [10:39] Mirv: I'm just going to hit it with dh_auto_configure -- LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH) unless you have a better idea [10:39] Saviq: yeah, got that [10:40] Saviq: just to be sure, the file only has to exist right ? No content is needed correct ? [10:40] vila, yeah, just touch it [10:40] cjwatson: sounds good enough [10:44] Saviq: fixed, let me know if the issue comes back, since it can be reproduced at will, it's hard to ensure it's really fixed :-/ [10:44] Saviq: what happened to the zero regression policy? [10:44] does not apply to design? [10:45] mandel: do you think we could land https://code.launchpad.net/~cjwatson/ubuntu-download-manager/fix-libdir/+merge/211699 fairly quickly assuming it passes CI? it's blocking some other packages in -proposed [10:46] seb128: ^- in case you were wondering why things are still stuck [10:48] Wellark, well, even with zero regression you have to make compromises if parts of the system change and others are not ready for that change ... else we would have to block landings forever [10:51] vila, will do [10:51] Wellark, depends on what you consider a regression [10:51] Wellark, getting the most confusing (for users) thing out of the way is probably not one === vrruiz_ is now known as rvr [10:53] cjwatson, thanks [10:54] ogra_: do you mind looking at system settling? It's not the first time we see that [10:59] (shorts_app/filemanager) [11:02] didrocks, once i got the top logs yep [11:03] thanks [11:07] psivaa: Mirv: did you get anywhere with the security tests that we'll be able to hand over jdstrand? [11:08] didrocks: still looking.. the unity-scope-loader crash has not occurred with 246 :/ [11:08] ok, so wrong lead… [11:08] didrocks: curious if 'util-linux from 2.20.1-5.1ubuntu16 to 2.20.1-5.1ubuntu17' on image 245 has any connections.. but Mirv dint see the failures in 246 [11:09] hmm [11:10] psivaa: indeed, I was preparing to downgrade it but I was not able to get the failures [11:11] psivaa: no, doesn't seems to be linked: http://launchpadlibrarian.net/169934738/util-linux_2.20.1-5.1ubuntu16_2.20.1-5.1ubuntu17.diff.gz [11:13] didrocks: Mirv: ok, looks like we need to ping jdstrand for this [11:14] i am digging further btw [11:14] thanks psivaa [11:14] yw :) [11:15] morning all [11:16] Mirv: btw, curious which user you ran the tests as? [11:16] davmor2: woke up twice today ? [11:16] vila: no this is me officially at work so I say morning on the important channels so people know I'm about :) [11:17] davmor2: :) [11:27] cjwatson, sure, let me take a quick look [11:28] cjwatson, done [11:30] mandel: oh, in a silo already? [11:31] cjohnston, oh, not in a silo, but I have a silo for udm and we can ask segio to add it to silo 15 [11:34] psivaa: as phablet (su - phablet) [11:35] Mirv: ok, that's what the tests in ci run as too :/ [11:35] sil2100, Mirv: I appreciate that touch fixes are important but desktop work, if you could assign the "desktop only" lines in there rather than skipping over them to assign touch ones that came after that would be nice :-) [11:36] * sil2100 didn't assign any silos right now [11:36] ok, click in silo 8 looks good, publishing [11:37] seb128: those two were assigned by Mirv - and besides, we don't assign any more silos right now as we are more or less ful [11:37] *full [11:37] sil2100, shrug, ok, I'm not freeing any of my silo in protestation then :p [11:38] No no no ;) [11:38] I guess I'll assign one of them at least, since a buffer of 3 seems to be still sane [11:38] thanks [11:38] I've 2 that are going through publishing [11:38] so those can come back to the pool soon [11:39] and done forget the towel :) [11:39] *don't [11:39] ;-) [11:46] cjwatson, will try to add it to silo 15, if not, will do a merge with one of the branches in that silo, does that sound good? [11:48] thanks [11:49] mandel: I don't think you can mean 15, though, that has gallery-app in it [11:49] cjwatson, sorry, one off error [11:49] cjwatson, 14 (i though it was 15) [11:50] cjwatson, we will at it to that silo, I'm testing it at the moment, so will trigger a rebuild, retest it and land it [11:50] hopefully in an hour or so we will be done [11:50] cool [11:51] sil2100: seb128: hi, I did assign only 1 after freeing 1. I'm sometimes a bit afraid still of assigning silos if I'm not specifically asked, even if it says "Yes" in the ready column, so that's why today I didn't assign silos for the new ones [11:51] I didn't assign the last line, but I did snatch one for qtwebkit since it'll take ages to build [11:52] Mirv: ACK ;) Better safe than sorry! [11:53] well, don't get too much in the habit of getting pinged, it's not scalable [11:53] I think we should show that we respond/assign silos when all infos are set [11:53] and look at that regularly [11:53] I did assign the unity8 one as per #ubuntu-unity as it's a blocker fix [11:54] (the volume key) [12:01] Mirv, k, I can ping more directly if you want ;-) === vila changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: none [12:04] seb128: I'll go with Didier's "being responsive" method :) [12:05] now we're at 18/20 full again though [12:06] three should become available ~soon [12:07] Mirv, I'm cleaning 011 [12:11] seb128: \o/ [12:11] seb128: I'll assign a silo for you then once that's free [12:12] you can nag Laney about landing001 [12:12] little ol' me [12:13]