[02:05] === trainguard: IMAGE 129 building (started: 20140714 02:05) === [03:35] === trainguard: IMAGE 129 DONE (finished: 20140714 03:35) === [03:35] === changelog: http://people.canonical.com/~ogra/touch-image-stats/129.changes === [04:51] that's all for now I think. upstart wasn't marked as ready yet, but assigned a silo anyhow [07:19] ogra_, champions! [07:27] :) [07:38] Mirv: ogra_: rsalveti: Here is the first MR for the SDK meta package -> https://code.launchpad.net/~bzoltan/ubuntu/utopic/ubuntu-touch-meta/add_packages/+merge/226635 [07:41] I wonder if we'll have ogra_ around today ;) Who knows if he's still not celebrating? [07:52] Hello... Just added a silo request for landing the welcome screen fix. [07:52] o/ [07:52] mvo_: can you assign? ^ [07:53] thx! [07:53] sure [07:53] camako: thanks for the fix! [07:54] mvo_, oh hold on for a sec... I need to check something.. [07:54] sil2100 sure... [07:54] ok [07:54] camako: just say when [07:55] mvo_, sure [08:00] mvo_, probably be an hour or two... still waiting on an MP to land on a branch... [08:00] sorry... shoulda checked first [08:01] xnox: I assigned your upstart a silo too, but I'd like to check if it's ok since it's not set to "Ready?" "Yes" yet? [08:02] sil2100: fyi, i'm running the missing tests for 129 now [08:03] brendand, \o/ [08:03] sil2100, i'm not such a big party guy :) but inded stayed up late :) [08:03] * ogra_ is still quite tired [08:04] bzoltan, commented on th MP [08:04] ogra_: not a party guy?!? [08:04] :D [08:04] * mvo_ remembers differently [08:04] well, i was watching at home with my GF ... we partied just a bit :) [08:07] ogra_: http://pastebin.ubuntu.com/7792430/ [08:08] psivaa: ok, thanks! I saw we're missing some test-suites there [08:10] sil2100: yea, one device misbehaved [08:12] sil2100, someone was complaining on the ML that his networking didnt work ... and there was a urfkill upload .... at the same time the failures started, i wonder if there is a connection [08:22] I'm looking at the changelog [08:25] ogra_: and here comes the other MR for the same package -> https://code.launchpad.net/~bzoltan/ubuntu/utopic/ubuntu-touch-meta/remove_friends_from_sdk_libs/+merge/226641 [08:26] bzoltan, giving me the list of deps wont help :) please chack they are not doing anything harmful (like making all input devices 0666 from a postinst script or some such ... ) [08:26] bzoltan: what about btw qtwebkit and qtscript, should they be removed at some point? [08:26] *check [08:26] Mirv: sure, why not [08:28] sil2100, FYI i had quite a few UI crashes over the weekend (on the promoted image) [08:28] ogra_: these packages are required to be installed on the app developer's machine. Right now they have to do it manually or hope that all these packages are pulled by an other package installed already on the system. So these are not new dependencies. [08:28] bzoltan, i dont care about dependencies ... [08:29] bzoltan, i know that autpilot on the phones makes input devices insecure for example ... that is something you dont want on a developer machine ... please make sure this cant happen we cant make all dev desktops vulnerable [08:30] ogra_: I do not know a lot about many things... but I expect that each package in the main/universe are safe to install. The SDK pulls in many-many packages. I have not reviewed each and do not review each update of all those packages. [08:30] (there is a difference between having developers install this by hand or pulling it in by default ... the latter needs a deeper audition) [08:32] ogra_: it is waaaay beyond my competence to review the hundreds of packages what the SDK pulls. I check this autopilot-desktop, but I really did expect that the releasing engineer or the landing team does check the packages before they are added to the archive. [08:34] it is beyond your competence to diff content of /dev before and after installing that package ? [08:36] ogra_: that one I can do ... but doing a full blown security audit on one of the biggest asset we develop is kind of beyond :) I am just paranoid ... [08:38] yeah, i just want to be sure we done install something superharmfull :) [08:38] ogra_: there was no diff between the contents of the /dev/ before and after installing the autopilot-desktop [08:41] ogra_: same here, but I really do expect the people who land the autopilot packages do that check. [08:41] well, if the expectation is their packages are only installed during testing ... [08:42] the autopilot-touch one surely assumes that [08:42] (at least parts of it do) [08:44] ogra_: With the sdk we distribute tests for the template/example apps, so the test tools are expected to be present. [08:48] Mirv: thanks. [08:56] Mirv: cihelp: can landing-005 be "de-allocated" it's no longer needed. Plymouth was uploaded direct into archive and stuck in new queue. and I will be uploading binNMU for casper&mountall direct as well. [08:56] ogra_: as cjwatson suggested -> The correct MR is here -> https://code.launchpad.net/~bzoltan/ubuntu-seeds/add_sdk_packages/+merge/226642 [08:58] xnox: done [08:58] cjwatson: thanks. [08:59] sil2100: do we just delete the spreadsheet row in this kind of situation, or what? [08:59] (after the silo finishes cleaning) [09:00] cjwatson: let me take a look, one moment [09:00] cjwatson: ok, so we have two approaches - we can either just remove it, or mark it as 'Rejected' in the Status field [09:00] xnox: have you tested the new plymouth on the phone? [09:00] But in this case I would just delete it [09:01] sil2100: what happens to subsequent rows that move up? [09:01] cjwatson: CI Train spreadsheet handles those correctly, all associations are made per-UID not per-line [09:01] So all should be ok [09:01] ok, good to learn [09:03] deleted ... er, hope that won't confuse things with silo 5 still cleaning, brain not switched on [09:03] ah, it's cleaned [09:04] bzoltan, i would just have tranferred that manually ... but yeah, thanks [09:46] psivaa, hmm ... what is "daily" (on img 129) [09:46] camako: how's the work on the branch going? :) [09:46] * mvo_ is off for lunch [09:46] psivaa, (5th from the bottom on http://ci.ubuntu.com/smokeng/utopic/touch/mako/129:20140714:20140712/9040/) [09:46] ogra_: ohh.. let me take a lool [09:47] sure, take a lol :) [09:47] sil2100, just waiting for the fix to be merged into the 0.4 branch... [09:47] work itself is done [09:54] Mirv: could you pleae upload http://s-jenkins.ubuntu-ci:8080/job/music-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.music_1.3.522_all.click to the store when you get a moment, thank you. [09:55] ogra_: i took care of it.. hope that reflects in the dashboard [09:56] and yea, i cant type, talk or even think properly today.. too much sunlight yesterday :D [09:59] sil2100: brendand: the tests completed. weather_app has one new failure [10:00] psivaa, yeah - i reran it and couldn't reproduce it [10:07] psivaa: thanks, I guess it might be a single case, can happen sometimes it seems [10:13] sil2100: brendand: ack, we'll see if it comes up with the next image [10:18] psivaa, yeah, seems gone [10:24] psivaa: brendand who can add reminders-app to the QA dashboard? [10:25] popey, i thought plars was on that [10:25] but seems it got forgotten or so [10:29] sil2100, Hi! [10:33] -> lunch [10:33] ogra_: about the qtdeclarative5-friends0.2 [10:33] bzoltan, well, as cjwatson said, you should talk to slangasek ... iirc he was working on that [10:33] ogra_: I have just made an MR to throw an error when a developer want to package an app what is using the Friends API [10:34] ah [10:35] i thought the plan was to keep the API and only drop the app [10:35] (but i'm likely the worng person ... steve works on that and knows more) [10:35] ogra_: I see the trunk ubuntu-touch.utopic has some change related to that. I think we should stop seeding the qtdeclarative5-friends0.2 [10:35] ogra_: I understood that we will keep friends-service on the phone as long as we support the 14.04 framework, but it should not be allowed by the SDK when targeting 14.10 [10:36] That's what removing it from sdk-libs should have done [10:38] (OK, perhaps with matching changes to the SDK itself) [10:39] om26er: hello! [10:39] om26er: good to have you around :) [10:39] sil2100, hah, I was about to tell you that ;-) [10:40] i'll be covering for davmor2 this week. [10:40] But I don't see any further seed changes that are needed at this point [10:41] om26er: we're still waiting for one fix to land first, i.e. for the hang-up issues in Mir [10:41] om26er: once this lands, we'll build a new image and we'll try looking it up dogfooding-wise [10:44] om26er: before that happens, maybe camako could use some help with the Mir silo - once it's ready :) [10:44] With testing it [10:44] sil2100, ok [10:45] popey: i take reminders-app is not a click package one? [10:45] psivaa: it is a click package and is now on the image by default [10:45] psivaa: http://people.canonical.com/~ogra/touch-image-stats/124.changes arrived in that image [10:46] popey: ack, i'd check how to enable those tests [10:46] popey: music app updated [10:46] Mirv: ythanks [10:46] -y [10:47] ywelcome [10:47] psivaa: is that "I would" or "I will"? [10:47] popey: consider I will :) [10:47] thanks [10:48] wasn't intentionally ambiguous :) [10:52] ☻ [11:09] cjwatson: has that change land landed already? On my utopic the ubuntu-sdk-libs still depends on qtdeclarative5-friends0.2 [11:11] bzoltan: The metapackage hasn't been refreshed (I assume slangasek will be doing that next; he was doing a lot of this late on Friday evening, I think), but the seeds look correct. [11:11] But we shouldn't be going around doing parallel not-quite-matching metapackage changes for things that have already been fixed in the seeds. [11:12] (Well, in general. I was considering doing a partial backport of a seed change to ubuntustudio-meta this week, but that's specifically to unblock a weird and complex transition ...) [11:13] cjwatson: OK, I will wait for slangasek with the deprecation of the Friends API. [11:17] mandel: could you please check silo-011 ? I can't publish currently as it says "2014-07-14 10:23:51,641 ERROR Some projects (mediascanner2, location-service, platform-api) that were in the silo configuration list were not built. Prepare either prepare the latest missing projects or use the ignore missing projects flag which will release the lock on them.". I assume you just need to rebuild the silo [11:17] mvo_, es, it is in my radar building atm [11:18] mandel: excellent, thank you! [11:18] mvo_, no problem :) [11:44] !cihelp how does one upload "additional source packages land" in a given assigned silo? [11:44] xnox: I am only a bot, please don't think I'm intelligent :) [11:44] cihelp how does one upload "additional source packages land" in a given assigned silo? [11:45] It's better to ask trainguards here ;) We don't get pings per cihelp === MacSlow is now known as MacSlow|lunch [11:45] xnox: dput. If you don't have permission, then either give us a source package, or put it in a PPA somewhere and we can do a copy-and-rebuild. [11:45] xnox: so... you have to dput those yourself to the silo ppa [11:46] The group with permissions to do so is managed by asac, but maybe we should ask him to include ubuntu-core-devs into that group [11:46] It results in rather a lot of mail [11:46] ok, i'm not in the team. And it ftbfs on virtualiased ppas. I'll put _sources somewhere on people. [11:47] I suspect it isn't worth further polishing silo upload permissions since that's all going to be replaced by the airline anyway ... [11:47] your call... tell me if i should do something [11:47] slangasek is also admin in case i am not around [11:47] I would simply add the core dev group as part of this group, it's just one click and might make things easier for everyone [11:48] sil2100: Did we decide on landing team shifts for this week? [11:48] yeah, airline should be easy in that respect. [11:48] cjwatson: yes, it's mvo_'s shift today :) [11:48] Tomorrow mine and on Wednesday is yours [11:48] OK [11:49] Ah yes, I see the wiki page is updated now [12:07] ogra_: there's an MP for it from last week, but there's a bit of disagreement about the results [12:07] this mir lockup is very frustrating [12:07] ogra_: I'm planning to take a look again today [12:07] plars, ah ... tell psivaa then :) [12:07] psivaa: & [12:07] err [12:07] popey, yeah [12:07] psivaa: ^ [12:08] popey, there is a landing from kgunn it seems ... [12:08] k [12:09] plars: ahh ack. appears we need to install some deps from the first look. dint yet figure out what [12:09] popey, ogra_, been waiting for the last few hours for the fix to automerge... [12:09] ah, crap [12:10] sil2100, is there any chance we can speed that up ^^^ ? [12:10] hmm [12:10] perhaps I should manually merge?? [12:10] The automerger is not part of CI Train, so I don't know - can't we anyway get the merge into the silo and build in the meantime? [12:11] Since the merge from CI Train only happens on the very end anyway [12:11] I cannot MP lp:mir/0.4 to lp:mir if the commit is not in 0.4 [12:11] I guess I can but.. [12:12] Ah, ok, since I saw a different MP in the MP list [12:12] https://code.launchpad.net/~vanvugt/mir/fix-1339700-both-0.4/+merge/226629 <- this doesn't look like a merge of lp:mir/0.4 to lp:mir on first look [12:12] right, that's not the right one.. row marked as "not ready" so pls ignore [12:13] just a placeholder for myself [12:13] Ah, ok [12:13] Someone like fginther would have to look at what's up with that auto-merge [12:14] cihelp: is there anyone around currently that could give us a status update how far a merge is in automerging? === MacSlow|lunch is now known as MacSlow [12:49] popey: can you try logging into here maps app and let me know if you can please [12:51] popey: just trying to figure out if it is the app/browser or the crappy connection [12:52] davmor3: hey [12:52] davmor3: will have to sign up, i dont think i have an account [12:53] sil2100, mvo_... spread sheet entry updated... requesting silo now... [12:53] I could do that I just couldn't login after [12:54] davmor3: i can't even sign in my desktop! [12:54] popey, davmor3, i think mandel knows more about that (not sure if also about the app, but definitely about "here" stuff) [12:55] davmor3: broken here, on desktop [12:56] Thanks as long as I know I'll go back to relaxing and not saving searches :) [12:56] heh [13:00] sil2100, what MP are you wanting to check? [13:00] fginther: hi! I think we're good now, right camako ? [13:00] fginther, yes we are good... [13:00] sil2100^ [13:00] sil2100, camako, ack [13:04] fginther, though not urgent any more, be nice to know why this didn't get automerged (didn't get Jenkins run on it, either) : [13:04] https://code.launchpad.net/~vanvugt/mir/fix-1339700-both-0.4/+merge/226629 [13:05] mvo_: ^ [13:05] mvo_: did you assign a silo? [13:06] ogra_, is not within my reach, I'm improving the location service, that should improve it [13:06] Ok, I'll assign it.. [13:06] mandel, ah, not the app ... k [13:06] (i thought so actually) === mhr3__ is now known as mhr3 [13:12] sil2100: in a meeting right now, I think I assigned it, but will check in a sec [13:12] camako, there are no jenkins jobs or configuration for lp:mir/0.4. What's the purpose of this series? [13:17] fginther, Curious... This is for Mir. We put Mir on a series/branch like this one... The second number is bumped every time there is an ABI break. And we release to our trunk from what ever branch we are on.... So 0.3.0, 0.4.0 (ABI break), 0.4.1 (no ABI break)....and so on === olli_ is now known as olli [13:17] mvo_: no worries, I assigned it [13:20] grrrr [13:20] * sil2100 irritated about some things [13:20] camako, so how does your development work? Once you create 0.4.0 (or 0.4.1, etc.) do you then line up a series of MPs to land into that one? [13:21] camako, and then when it's ready, propose a merge of lp:mir/0.4.0 to lp:mir? === greyback is now known as greyback|lunch [13:21] fginther, correct [13:22] camako, how does lp:~mir-team/mir/development-branch fit into this? [13:22] fginther, the MPs are from our devel to 0.*.* [13:23] fginther, basically we check into devel... then we move it to a series 0.x... then we MP from there to trunk [13:23] fginther what 0.x branch/series is determined by the ABI breakage [13:25] sil2100: I'm back so if you haven't look at it already I can do so now [13:25] camako, ok, so once 0.4.0 is merged to trunk, is it 'closed'? and the next work happens on 0.4.1 or 0.5.0? [13:26] mvo_: as mentioned, I assigned it :) [13:26] t [13:26] ta [13:26] fginther, "next" is determined by ABI break.. It could be 0.4.1 if nothing has been broken since 0.4.0 or it could go to 0.5.0 if we have broken the ABI [13:26] camako, jenkins has to know what lp branches to monitor for MPs. So when the series changes from 0.4.0 to 0.4.1, the job configurations need to be created for that new branch [13:27] * camako didn't know that [13:27] cihelp - please copy source only: upstart_1.13-0ubuntu1.dsc from ppa:canonical-foundations/upstart-daily into Silo 003 and mark PPA for building. [13:27] $ ./copy-package -n -d ubuntu -s utopic --ppa canonical-foundations --ppa-name upstart-daily --to-ppa ci-train-ppa-service --to-ppa-name landing-003 upstart [13:27] fginther, this process is new and a bit immature... still needs polishing... [13:27] xnox: I will take care of this - its best to ping trainguard btw, we all highlight on it [13:27] fginther, is the config done by us (the mir team) or do we have to let you guys know? [13:28] camako, no worries, I'm just trying to understand it better to come up with a way to handle this with the jenkins jobs [13:28] mvo_: had no idea. Why topic says "Vanguard: cihelp" then? or what's the difference between trainguard vs vanguard? [13:28] fginther, do you know if it's in any way possible to get the jenkins coverage plugin to link through to the actual source code? [13:28] fginther, most projects i've seen so far don't have that [13:28] xnox: its because I'm too lame to set the topic correct :/ [13:29] mvo_: also FAQ doesn't say how to request additional source inclusion at all. Would be helpful to document it there, as to how to properly request such things =))))) [13:29] ev: https://errors.ubuntu.com/ broken and not returning any data, someone said you were the person to notify. [13:29] mvo_: ah =))))) [13:29] xnox: I think that's the vanguard for other CI things, not the CI train [13:29] cjwatson: oh. i see. [13:29] xnox: "CI Train Sheriff" is the one you want for the latter [13:29] camako, it's easy enough to propose an MP to update a jenkins configurations from lp:mir/0.4.0 to lp:mir/0.next.next. I can show you how this is done [13:29] xnox, yeah, you want the sherriff ... not the deputy ;) [13:29] -r [13:29] Because metaphors are never knowingly undermixed around here, apparently [13:30] robotfuel: GAHH. On it. [13:32] xnox: well, this is a CI channel, so the Vanguard is for CI stuff - for CI Train stuff there's CI Train Sheriff [13:32] xnox: as the topic says ;) [13:32] robotfuel: webops is on it [13:33] fginther, pls do [13:34] brendand, I don't know how that is done, have you talked to alesage? [13:34] fginther, not yet, but i will [13:38] trainguards: Hi, could someone please start a rebuild of silo-014? [13:39] ChrisTownsend: sure [13:39] mvo_: doing this ^ [13:40] sil2100: oh, ok. I just clicked on "build" [13:40] Oh [13:40] THen please do ;) [13:40] sil2100: mvo_: Thanks! [13:40] Thanks! [13:40] sil2100: if you could do the upstart package copy/upload in silo-003, that would be great, I got a permission denied error [13:40] mvo_: hm, let me try [13:46] mvo_, xnox: I uploaded the package to the PPA, now we need to wait for it to build and then run watch-only [13:47] looks good, thank you all =) [13:48] sil2100: thanks! I will wait for the build then. is it possible that I get added to the people with upload permission (ie ~ci-train-ppa-service)? [13:48] mvo_: as I mentioned, this team is managed by asac and slangasek ;) Only they can add people - I would opt for adding the whole ubuntu-core-dev team though [13:49] all trainguards should be in [13:49] I will add mvo for now [13:49] thanks [13:49] Since it make sense for core devs to be able to upload, as any core dev can anyway do landings as they wish [13:49] done [13:50] yes, core-dev was the plan to do, but read above that cjwatson had concerns about emails getting sent to all core-devs abvoe [13:50] discuss with cjwatson and slangasek ... slangasek is admin so whate3ver you agree he can just do === greyback|lunch is now known as greyback [14:02] the potential e-mail flood could be avoided by setting a mailing-list as the contact address for the team, though indeed, may not be worth doing as we'll replace everything soon enough anyway [14:11] * sil2100 is angry at LP API [14:15] sil2100: What's wrong? [14:16] stgraber: ~ubuntu-core-dev has had a mailing list set as its contact address for years, but a good deal of junk still gets through for teams it belongs to. [14:17] Maybe that's a bug somewhere ... [14:21] 006 is conflict-able, yes? === barry` is now known as barry_ === barry_ is now known as barry [14:21] mvo_: Hi, I'm watching the status of silo-014 in the dashboard and it hasn't updated at all as of yet. I'm not familiar with how long things take for this, so should the status have been updated by now or am I being impatient? [14:24] ChrisTownsend: packages are build and ready for testing afaict, what status are you currently expecting? [14:25] ChrisTownsend: the normal workflow is to test them now and once that is done I can publish - or am I missing something here? [14:25] ChrisTownsend: oh, I do [14:25] ChrisTownsend: hold on a sec [14:26] mvo_: Ok [14:26] mvo_: I'm needing a rebuild [14:28] plars: you about? is "reminders on the qa dashboard" on your plate? [14:28] charles is getting a ppc unit test failure and wants to investigate further cihelp, I recall that there are boxes somewhere for this kind of thing? [14:29] ChrisTownsend: I triggered it now with different parameters (the previous one apparently did not had enough --force options). [14:29] alesage: https://wiki.canonical.com/InformationInfrastructure/ISO/BuildInfrastructure/PorterBoxes [14:29] charles: ^- [14:29] mvo_: Ok, thanks [14:29] * charles clicks [14:30] cjwatson, thanks [14:30] charles: once you have access (ask #is if not) you can use "schroot -c utopic-powerpc", and if necessary you'll have limited "sudo apt-get install" capability in there [14:31] Right now it's a big shared chroot rather than anything cleverer, though usually that's not a problem [14:31] plars: bug 1307542 [14:31] bug 1307542 in Ubuntu CI Services "Add reminders app to image touch testing" [Undecided,Confirmed] https://launchpad.net/bugs/1307542 [14:35] popey: right, just need to sort out a few things with the merge on our side [14:36] popey: I could put it in right now, but I suspect we're missing something because I'm told the tests all pass, but most fail when I try them [14:43] plars: ok, we need to fix broken tests then, balloons ^ [14:44] I would need to see plars's output.. they should work [14:44] popey: well, like I said, it could be that we're just missing some dependency or something. I pinged leo about it earlier [14:44] balloons: take a look at http://q-jenkins.ubuntu-ci:8080/job/plars-smoke-daily-test/4/#showFailuresLink [14:45] plars, I see the problem right off the top. This has to be run as python3 [14:45] stgraber: queuebot seems a bit quiet [14:45] it is hung over ... it is a germany fan ;) [14:46] balloons: oh, I thought phablet-test-run was running them all with python3 already [14:46] plars, it has a bug in it causing things to run py2 when they shouldn't. maybe you are hitting it? [14:47] Laney: restarted [14:47] danke [14:47] either way, make sure it runs as py3 and things should go better [14:50] balloons: isn't that something controlled by the test, not me? [14:50] plars, no you can run it with autopilot or autopilot3 [14:51] balloons: we are running it with phablet-test-run [14:56] plars, ok, well sparing taking about how you are running it, it needs to run with autopilot3 ;-) [14:56] I believe on the dashboard the tooling is different and phablet-test-run is not invovled [14:56] balloons: I know, I'm just saying that I don't have any control over that unless we put in some weird hack for working around this in reminders [14:57] balloons: we have been running all autopilot tests with phablet-test-run for a very long time now, because that's how everyone else is supposedly running it [14:57] plars, you don't have any control over what exactly? are you concerned this won't run properly on the dashboard? [14:57] balloons: which dashboard are you talking about? [14:57] ci.ubuntu.com [14:57] let me check something [14:57] balloons: ci.ubuntu.com is just a dashboard to display the results, the tests themselves are run with phablet-test-run, which is supposed to select the correct autopilot [14:57] balloons: for some reason, it's selecting the wrong one it seems [14:58] plars, really phablet-test-run is used? that's surprising to me [14:58] looking at it now, but I'm about to have to go to a meeting. I suspect this is something wrong with reminders-app tests since the others behave [14:58] balloons: that has been the case for quite a while [14:58] mm.. plars I thought maybe the debian/control file used py2, it doesn't [14:59] balloons: looks like the change to use phablet-test run was since january or so [14:59] plars, mm, looks like one of the issue may have been fixed: https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1327325 [14:59] Ubuntu bug 1327325 in phablet-tools (Ubuntu) "phablet-test-run will fail if the python3 import prints something to std" [High,Confirmed] [14:59] balloons: I'll play with it some more after this call [14:59] balloons: that would do it [14:59] plars, phablet-test-run is just weird in how it determines py2 and py3.. I don't like it [15:00] balloons: there's a warning about ubuntuuitoolkit [15:00] The ubuntuuitoolkit.emulators module is deprecated. Import the autopilot helpers from the top-level ubuntuuitoolkit module. [15:00] I'm surprised other tests are not affected by this [15:00] plars, yes, that's ok [15:01] balloons: but from the title of the bug, it makes it sound as if that could be the source of the problem [15:01] several apps have the same warning and will need to be migrated.. but support still exists [15:01] plars, yes I'm assuming it or something like it is the source issue [15:01] I've run into it in the past. [15:02] let's chat after meetings ;-) [15:03] kenvandine, the next build failed the same way on gallery [15:03] :/ [15:05] sil2100, can you help us figure out why build failed as unstable like http://s-jenkins.ubuntu-ci:8080/job/generic-mediumtests-utopic/1624/console [15:05] sil2100, 1625 fails in a similar way [15:05] for a diff project [15:06] sil2100, same problem i was seeing when the network was failing on the devices [15:07] I doubt it [15:07] click on autopilot-testrunner-otto-utopic-XXX [15:07] and then you see the real failure [15:10] Laney, but that job is successful [15:11] where? [15:11] https://code.launchpad.net/~saviq/ubuntu-system-settings/fix-wizard-sim/+merge/226555 [15:11] that's the MP [15:11] kenvandine, its failing on the about page, I wonder if phone number broke the test [15:12] kenvandine, like when there is no sim or something [15:12] pmcgowan, where do you see that failure? [15:12] kenvandine, http://s-jenkins.ubuntu-ci:8080/job/autopilot-testrunner-otto-utopic/1360/ [15:12] shows 2 failures [15:12] kenvandine: I followed a trail from the MP and got to https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/2161/ [15:12] which is the same [15:12] hmmm [15:13] It's a real bug I think, was looking at it earlier but didn't reproduce [15:14] see recent scrollback in #ubuntu-desktop for example [15:14] I asked pitti for insight but didn't get a reply ;-) [15:15] (we first noticed late on friday) [15:15] (could be related to py3 AP test porting) [15:16] mvo_, sil2100, can I get a silo for line 31 please? [15:16] (one way to verify that would be to propose an MP with that branch reverted and look at the testing on that) [15:16] Saviq: mvo_'s on it :) [15:16] ok thanks [15:17] i doubt this has anything to do with adding the number [15:18] kenvandine: I'll try to look in a moment, but as I am not really well oriented in the CI infrastructure there, I guess someone from cihelp might be a better match [15:18] although that branch itself had successful CI [15:18] so ... [15:18] yeah, it did [15:19] i guess we need to bisect it [15:19] doesn't happen locally [15:19] so, not fun [15:19] but it looks like something with the updates stuff [15:19] it's when trying to get a handle for dbusmock's system bus [15:19] you get a Connection refused [15:19] yeah [15:20] that's why I figured pitti would know [15:21] kenvandine, I think perhaps the error is misleading, the failing line is lookign for what used to be the first info item [15:24] kenvandine, perhaps I am wrong... [15:24] lemme push a branch to get it checked by CI [15:32] bzoltan, cjwatson: I haven't changed the metapackages yet for friends; mhall119 wanted me to wait so it could be announced on developer.ubuntu.com [15:34] slangasek: in my team call right now I'll bring it up [15:34] mhall119: cheers :) [15:35] Laney, are you going to remove the subscriberNumber from about and test that? [15:35] * kenvandine really doesn't think that's related [15:35] first I'm reverting the py3 tests branch [15:35] ah [15:35] then we can try other ones [15:35] xnox: what was the "additional source package" for the landing in question? upstart? [15:36] aha, it was [15:37] kenvandine: https://code.launchpad.net/~system-settings-touch/ubuntu-system-settings/test-reverts/+merge/226691 use this one for testing if you like after I've gone EOD [15:38] Laney, thx [15:38] both of the failures seem related to dbus SystemBus connections [15:39] yeh [15:47]