=== Ursinha-afk is now known as Ursinha [00:13] bfiller, just tried assigning your latest silo but one of the URLs is a branch instead of a merge. === robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #113 promoted | CI Train Sheriff: trainguard | Known issues: http://bit.ly/VI2SEl knows your silo status before the spreadsheet does. [02:04] === trainguard: IMAGE 118 building (started: 20140708 02:05) === === renato_ is now known as Guest11141 [03:02] robru: hello [03:02] bzoltan, hiya [03:02] robru: What can I do to push the UITK out from the proposed pocket? [03:03] bzoltan, did you get my email? I filed a bug with the pastebin of the failing test that's blocking it [03:03] robru: I check my mails [03:11] robru: I have run the AP tests for the online_accounts -> http://pastebin.ubuntu.com/7763215/ [03:12] bzoltan, uhhh, I dunno. [03:12] bzoltan, maybe it just needs to be re-run then? [03:12] let's see if I have permission to do that... [03:12] robru: most of the times when I see an AP failure a reboot and a re-run helps [03:14] robru: and also make sure that he /home/phablet/autopilot/ubuntuuitoolkit is empty, so the release candidate UITK tests from the -autopilot package are used and not the /home/phablet/autopilot UITK tests what are from the actual release. [03:14] bzoltan, I wasn't running this locally, that pastebin is from the proposed-migration jenkins thing. [03:15] yummmy, apparently I have the power to restart those jobs... [03:15] robru: I know that. I just wonderif that test environment is properly set up. [03:15] robru: use the force :) [03:15] bzoltan, no idea what the setup looks like. however the test is marked as 'regression' so it used to pass last time uitk did a release. [03:17] robru: let's see what the re-run does... failing tests in my experience are rarely the sign of regression but flaky tests, misconfigured test environment or simple broken device what needs a reboot. [03:24] bzoltan, nope, same failure. no idea who we should escalate this to, either [03:25] robru: to me, apparently ... we have to wait for t1mp [03:25] bzoltan, alright, sorry, did all I could. [03:26] robru: Is there any other failure, or is that the only one? [03:26] bzoltan, yeah just the one failure [03:27] robru: I would land the UITK with that [03:27] bzoltan, it's not up to me, though ;-) I already clicked publish, it's stuck in proposed. if you want to push it through you'll have to appeal to an archive admin like infinity or cjwatson [03:30] robru: I will ping both infinity and cjwatson ... I know it is not up to you. I just think that this UITK is a super big one to land and it does not make much sense to block it by a test what fails on the CI but does not fail when I run locally [03:39] === trainguard: IMAGE 118 DONE (finished: 20140708 03:40) === [03:39] === changelog: http://people.canonical.com/~ogra/touch-image-stats/118.changes === [04:12] "Object not found with name 'QQuickView'", mmkay. probably some sort of test environment issue? [04:14] but different on i386 [04:29] Mirv: robru: I have reflashed my device with image 118 and re-run the online_accounts_ui tests. All OK [04:49] cjwatson: infinity: Mirv: robru: I would definitely call this case an exception. I can not reproduce the failure and this failure did not show up in any of the 8 test rounds I have run in the last 5 days. [05:22] robru: hey, I've had a silo for a couple of days now, but I've been held back by build issues etc. Should I release mine or is it ok to hold on to it. The build issues et. al will be resolved (my) tomorrow [05:26] veebers, I don't see any pressing need to free yours, but thanks for letting me know, notied [05:26] noted [05:26] robru: sweet, cheers [06:53] mandel, hey, what's the status of the u-d-m abi change silo? [07:18] Mirv: sil2100: I need your help with the UITK landing. There must be something wrong with the CI test environment. I have logs from 8 run of the online_accounts_ui tests and they are all OK. [07:18] bzoltan1: hi! Just wanted to ping you about the failing autopkgtests ;) [07:18] bzoltan1: I don't know specifically what's different in autopkgtests test environment from eg image testing or lcoal testing [07:19] sil2100: I am pinging people all around all morning :) [07:19] bzoltan1: I think we might need to bring in pitti, he'll probably know the most [07:19] Mirv: Same here ... I think that failure is false and should be ignored or disabled. [07:22] sil2100: Mirv: I am just worried that this will delay the UITK landing... and I can not even do anything. Why not to release it and fix the environment later. If the header would be regressing it would cause test failures all over the apps... it does not. [07:23] we can't do any overrides either, that's why we need at least someone familiar with the autopkgtest infrastructure [07:23] one good test would be to try to run the same tests with the previous version of the UITK now [07:23] to see if something changed in the infrastructure/environment/other packages that causes this [07:28] bzoltan1: is the main problem in the autopkgtest starting already with "/dev/autopilot-uinput" cannot be opened for writing? [07:29] bzoltan1, Mirv: btw. I see this test started failing earlier already [07:29] thostr_: yay for GUI hotspot functionality! :) [07:29] So it is indeed unrelated [07:30] Mirv: can I get a silo for it? [07:30] sil2100: I have no idea what that "/dev/autopilot-uinput" is whatit is used for [07:30] thostr_: yes, you have 003 [07:30] bzoltan1, Mirv: or maybe not, hm, as the last failing run was 12 hours ago - I wonder when we published UITK to the proposed channel [07:30] Mirv: oh, and it will be disabled on n4 by default for now... as this triggers a driver issue meaning it doesn't work there fully yet [07:30] thostr_: ah, ok [07:31] Mirv: so we land it disabled, then we can at least easily test on bq device [07:31] sil2100: it was rerun in the morning [07:31] bzoltan1: actually I see this error during successful tests as well, so hm, unrelated [07:31] The main failure is the Header missing [07:32] sil2100: note that the error is different on amd64 [07:33] Mirv: they look the same to me when comparing two logs [07:34] bzoltan1: so running those tests with your new UITK locally on a device results in no failures? [07:34] hey, where did the QQuickView thing go... [07:35] sil2100: oh, right, that was earlier run, now they are the same in the latest run. there have been several reruns [07:35] thostr_, hum, are you doing a landing for settings? the mp you listed is not even approved, settings are in a silo and we have at least 3 landings to do then, would be nice to sync up on those [07:36] sil2100: in #85 for example it's QQuickView on amd64, not Header [07:36] speaking of which [07:36] mandel, if you don't free that u-d-m silo I'm going to do a landing and force you to rebuild u-s-s in your silo ;-) [07:36] seb128: this is for another testing round first [07:37] ah, it's annoying the conflicts detector only lists the first conflicting silo [07:37] seb128: or wait... which mp are you talkign about? [07:37] Mirv: you can use the bot to get more info ;) [07:37] thostr_: probably one of that in Finalizing transfer indicator [07:37] But yeah, I can change that today I guess! [07:38] Mirv: yeah, but that has been approved [07:38] thostr_: ok this one probably https://code.launchpad.net/~thomas-voss/ubuntu-system-settings/add-option-for-cell-and-wifi-id-reporting/+merge/225847 [07:38] in add location detection via cell id to settings [07:39] Mirv: yes, let's wait with that one [07:42] thostr_, I was speaking about l25 [07:43] thostr_, but it's ready "no", so no worry, I'm just giving you an headsup that we have some landing lined up for the next days [07:43] thostr_, btw do you still have the flight mode one on your list? [07:43] seb128: yes, but still waiting for urfkill to be confirmed to be fixed [07:43] k [07:45] sil2100: as you say. Those tests are OK when I run them on the device [07:53] bzoltan: then let's maybe indeed poke pitti, maybe he'll have any ideas [07:53] bzoltan: could you join #ubuntu-devel? I'll poke him there [08:13] psivaa, do you think we need to be starting the builds a little earlier in order to get results in time for the meeting? [08:13] psivaa, it seems we're not longer able to get a full run in the time available [08:14] Did it fail again? [08:14] Since there should be no reasons for the test results not finishing in time, besides some device hang-ups or something [08:16] sil2100: brendand: it wasn't the time constraint. but different types of failures in flashing, unlocking screen etc. holding up running a number of tests [08:18] sil2100: one such incident for today is 'I: Unlock failed, script output: 'initctl: unable to determine sessions', which we saw earlier too once or twice. keeping the affected device for further debugging [08:28] psivaa: ok [08:47] bzoltan: I'm not comfortable overriding this when it's just a hypothesis that it's an environmental failure, sorry [08:47] cjwatson: we got the problem [08:47] cjwatson: http://bazaar.launchpad.net/~online-accounts/ubuntu-system-settings-online-accounts/trunk/view/head:/tests/autopilot/online_accounts_ui/tests/test_online_accounts_ui.py#L72 [08:48] OK. Still catching up on IRC from the several different channels this conversation is spread across [08:48] The tests are run with QEMU what is actually "Desktop" [08:55] sil2100, hey, can I have a silo for line 28 ? [08:55] oSoMoN: one moment o/ :) [08:59] ogra_: sil2100: the logs are here: http://people.canonical.com/~psivaa/ [08:59] ogra_: check with rsalveti about cron I'm sure it is part of his fix for alarms I'm sure I saw him talk about cron [09:01] davmor2, yeah, grepping through the changelogs it seems to be seeded since a while already [09:01] ogra_: yeah blame rsalveti [09:01] no, no ... way before the clock fixes [09:01] I didn't add it for sure [09:02] right [09:02] we seem to have it since forever [09:02] i dont get why it wasnt on the image in malta when i looked for it [09:03] ogra_: one thing to knock off your whiteboard at least though right [09:03] davmor2, no, that only means i need to work faster to get the unwanted cron jobs diverted [09:09] sil2100, we can land it - just need a lander [09:11] popey: do the honours please https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1338956 [09:11] Ubuntu bug 1338956 in Ubuntu Calendar App "Date/time changer hidden when textfields have focus" [Undecided,New] [09:12] done [09:17] sil2100, who can publish silo's then? [09:18] brendand: o/ [09:18] brendand: I can :) [09:18] brendand: is the silo tested? [09:20] sil2100, yes - MR approved, etc, etc [09:23] brendand: has the testing plan been executed and no regressions seen? ;) If yes, then move to the silo sheet (sheet for silo 14) and set testing to 'Done' === vrruiz_ is now known as rvr [09:32] ogra_, adb is out, right? how do I reboot in the bootloader? [09:32] ogra_, or is that just for the shell etc? [09:35] brendand: ok, I guess you did test it properly, yes? Just need a double confirmation and I publish [09:37] sil2100, i updated the sheet, ready to go! [09:37] o/ [09:38] sil2100, did you see all the testing finished - 99.5% :) [09:41] brendand: published :) Now we need to wait for it to move out of proposed [09:42] mandel, nothing landed yet [09:42] ogra_, ah, ok [09:42] so nothing changed either ;) [09:42] ogra_, I though it was there already :) [09:43] nope, i can only land it once we can actually change the password [09:43] and that is blocked by an adduser bug [09:43] ogra_, one tiny little question, I keep forgetting how to resize the system so that I can develope in the phone, can you refresh it for me (or point me to a wiki) this time I'll take notes :) [09:43] (mentioned in my mail) [09:43] ogra_, sorry, I must have missed that email [09:44] mandel, reboot into recovery and use resize2fs against the img file in /userdata [09:46] ogra_, with adb shell ?? [09:47] in recovery, yes === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train Status: #113 promoted | CI Train Sheriff: trainguard | Known issues: http://bit.ly/VI2SEl knows your silo status before the spreadsheet does. [10:48] Mirv: I have the refactored the autopilot tests MR ready in the CI Train sheet [10:48] Mirv: in line29 ^^ [10:53] bzoltan: ok [11:05] bzoltan: building https://ci-train.ubuntu.com/job/landing-014-1-build/102/console [11:05] Mirv: thanks [11:05] hmmm [11:05] * sil2100 feels tempted to build a new image with the sensor fix [11:06] ogra_: I know that will be a bit of a waste without UITK moving out of proposed yet, but don't you feel tempted as well to see test results without sensor madness? ;) [11:08] ogra_: could we maybe kick a new image like in ~1h? I'm saying 1 hour since I want the recently released stuff to land in the archive, so that we don't have any partial transitions [11:35] sil2100, should I worry about silo 12?? or does it seem that everything is ok? [11:38] sil2100, done ... [11:44] === trainguard: IMAGE 119 building (started: 20140708 11:45) === [11:45] mandel: let me see [11:45] sil2100, thx [11:45] mandel: ah, sadly it will be blocked in proposed for some time [11:46] sil2100, may I know why? (mainly for me to understand) [11:46] mandel: we had a test regression in ubuntu-system-settings-online-accounts, so all packages that force running these autopkgtests will now fail [11:46] mandel: (it's due to the UITK landing) [11:46] mandel: but bzoltan and others already have a fix pending for release [11:47] So all should be unblocked soon [11:47] sil2100, ah, ok, but there is nothing for me to do, right? I just have to have patience, correct? [11:47] I have plenty of it :) [11:47] will #119 have the sensors fix? [11:48] sil2100: I'm working on running that test locally so that I can arrange for that test to be ignored earlier than the landing [11:48] (Since apparently it's quicker to have me run tests on my laptop over slow ADSL than it is to land a test fix in the archive; don't ask me, I just work here) [11:49] It's out of the question to try to upload that fix? [11:50] I have no idea, all I get told is that that will delay UITK by another day [11:50] Which sounds like hyperbole to me but whatever [11:50] Mirv: I have added the silo14 to my device and run the `phablet-test-run online_accounts_ui` it got 4 OK results very quickly [11:51] bzoltan: o/ [11:51] cjwatson: well, it seems we'll be landing the fix now I guess [11:51] sil2100, can we publish silo 18, please? [11:52] oSoMoN: doing :) [11:52] cjwatson: I could probably try running it ~easily if you like [11:53] So "that would block the UITK for an other day" is simply untrue then, shame I wasted all that time [11:53] Huh [11:53] bzoltan: published [11:53] Laney: No, I have a working setup now [11:53] kay [11:53] But I'm not going to bother if silo 14 is landing :) [11:53] bzoltan: it's the fix for the failing autopkgtests, right? [11:54] cjwatson: let me double-confirm if the description and my memory is telling the truth [11:54] *is/are [11:54] sil2100: it is a branch what refactored the autopilot tests for the online_accounts_ui [11:54] It's test fixes from the changelog [11:55] cjwatson: please do not. I did not expect this MR to land that fast :) let's see the UITK autopkgtests after this change is in [11:55] * sil2100 off to lunch [11:55] o/ === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #113 promoted | CI Train Sheriff: trainguard | Known issues: http://bit.ly/VI2SEl knows your silo status before the spreadsheet does. === cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #113 promoted | CI Train Sheriff: trainguard | Known issues: http://bit.ly/VI2SEl knows your silo status before the spreadsheet does. === alan_g is now known as alan_g|lunch === renato_ is now known as Guest99235 === fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #113 promoted | CI Train Sheriff: trainguard | Known issues: http://bit.ly/VI2SEl knows your silo status before the spreadsheet does. s-jenkins being prepped for restart === greyback is now known as greyback|away === alan_g|lunch is now known as alan_g [13:03] fginther: when will jenkins be back? [13:03] ogra_, there are several ubuntu-touch seed merge requests in the sponsoring queue, could you look at those? [13:04] ogra_, ~sergiusens/ubuntu-seeds/utopic_qml-sync-monitor ~ted/ubuntu-seeds/pay-service ~xnox/ubuntu-seeds/touch-content-hub [13:05] popey, shouldn't be more then 30 minutes now [13:11] seb128, hmm, these should all have been synced [13:11] ogra_, "synced"? [13:11] merged, sorry [13:12] ogra_, if they did please mark them as such, that works too ;-) [13:14] === trainguard: IMAGE 119 DONE (finished: 20140708 13:15) === [13:14] === changelog: http://people.canonical.com/~ogra/touch-image-stats/119.changes === [13:14] Yaay, now for the test results === boiko_ is now known as boiko [13:16] sil2100: hi, could you please publish silo 005? [13:16] sil2100: Is there anything i should do with the silo5 to land the address-book AP fix? [13:16] sil2100: oh man I didn't get to annoy ricmm with incessant pinging or anything, /me shakes his fist at the world [13:17] boiko: :D [13:17] Ah! [13:17] sil2100: no pressure :D [13:17] boiko, bzoltan: sorry guys, it seems the spreadsheet was b0rken and it didn't update the state [13:18] boiko, bzoltan: the cell with some formulas was empty and we simply didn't see it as ready ;) Fixed it and landing [13:18] sil2100: great! thanks a lot! [13:18] sil2100: No worries :) the UITK is still blocked by the online-accounts anyway [13:19] sil2100: Am I still looking at 118 for promotion or should I change over to 119? [13:19] davmor2: ah ha! How far are you with testing 118? ;) [13:20] sil2100: mostly done but if 119 has better results on auto tests then 119 would be the better candidate right? [13:20] davmor2: there are some differences, but if you didn't go to far with 118 I guess 119 would be better (but we need test results first anyway!) [13:20] Yeah [13:20] But still, it's like 2 hours away from getting ready [13:21] sil2100: yeah that is fine I'm here till 20:00 BST anyway [13:21] and the match doesn't start till 21:00BST so ogra_ and still promote :D [13:22] s/and/can [13:22] ;D [13:23] ;) [13:23] heh [13:24] Too bad we won't have an isolated image with UITK, but geh! We have a whole week to fix stuff, right?! :) [13:25] sadly the online-accounts still failed (the new one) [13:26] although looks funny, it didn't really run properly? [13:27] elopio: sil2100: https://code.launchpad.net/~elopio/ubuntu-system-settings-online-accounts/clean_tests/+merge/225437 introduces "import ubuntuuitoolkit" but the package does not depend on ui toolkit === cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #113 promoted | CI Train Sheriff: trainguard | Known issues: http://bit.ly/VI2SEl knows your silo status before the spreadsheet does. [13:29] "could not import package online_accounts_ui: No module named 'ubuntuuitoolkit'" [13:30] it's being fixed already [13:30] see #ubuntu-release [13:30] ah [13:32] popey, it's back [13:33] sil2100: I need a silo for line 27 when you have a chance [13:33] thanks fginther [13:34] mvo_: ^ :) [13:34] sil2100: we have free silos again? I'm in! [13:34] mvo_: 2 free silos:O ! [13:35] sil2100: thanks, I pay close attention again then :) [13:35] sil2100, the fix got landed, i cleaned the silo myself \o [13:36] sil2100, from this day forth, let us be free of weird rotation issues! === greyback|away is now known as greyback [13:38] brendand: indeed! 119 should have nicer test results :) [13:39] sil2100, i tested gallery-app twice with my fix landed, and it didn't fail. so hopefully (*hopefully*), we should only have 2 failures in the next image [13:39] (famous last words) [13:40] sil2100: we had a bumpy road for this UITK landing ... but now I see the light at the end of the tunel [13:40] bzoltan, that might just be a train approaching ... [13:40] :P [13:40] ogra_: kind of expected this answer :D [13:40] haha [13:42] ogra_: it is a bit hectic that we had to fix like six projects in order to land our innocent UITK [13:42] yeah, i know what you mean [13:42] bzoltan: is the light moving? If not then it's possibly the eurostar still stuck in the tunnel from yesterday :D [13:43] davmor2: LOL :) but eurostar has two lights [13:44] hahaha [13:48] * sil2100 is excited [13:49] about trains ? [14:12] sil2100, I can has silo for lin 31 please? [14:12] or are we down on silos? [14:12] we could give up 9 if needed [14:13] Saviq: we have one left, but we'll free it up if we need [14:14] sil2100, thanks [14:14] sil2100, FWIW we should be able to land that one, too, soon [14:15] sil2100, Saviq: I'm going to m&c one in the next half an hour as well [14:15] Saviq: would be awesome [14:15] seb128: I saw that, thanks o/ [14:15] yw! === fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | CI Train Status: #113 promoted | CI Train Sheriff: trainguard | Known issues: http://bit.ly/VI2SEl knows your silo status before the spreadsheet does. [14:17] sil2100, mandel: I'm doing a m&c on silo 012 even if settings is still in proposed, Laney is working on solving the online-accounts test issue and I want to line up another landing for settings [14:17] * sil2100 needs to make some coffee [14:17] seb128: ACK [14:17] seb128, superb, I'm happy with that :) [14:17] sil2100, hey, can I have a silo for line 32? it’s an oxide landing, no MR associated [14:17] mandel, ;-) [14:26] fginther: http://s-jenkins.ubuntu-ci:8080/job/ubuntu-calculator-app-autolanding/ is that actually working? seems to be taking an age [14:29] popey, looking [14:29] ta === alan_g is now known as alan_g|tea [14:30] * popey goes to get fixed car from garage [14:30] oSoMoN: will get you a silo once we have the chance ;) [14:30] popey, looks to be finishing now === alan_g|tea is now known as alan_g [14:48] sil2100: Mirv: the QtC plugin in the silo17 is good to go [14:59] sil2100, looks like there are a couple of free silos now, can I get one for line 32, pretty please? [15:00] oSoMoN: You can get mine if the silo17 is landed :D [15:07] mvo_, err ... i see gallery-app being uploaded, did the former upload already migrate out of -proposed ? [15:08] ogra_: uh, that may well be my mistake, sorry [15:08] just make sure nobody releases a click for it [15:09] ogra_: I wonder if there is anything we could do in the spreadsheet to protect against such mistakes [15:09] hmm perhaps ... we dont have such issues that often though ... (and click releases are fully manual atm anyway) [15:10] yours wasnt a mistake ... as long as nobody releases the click [15:11] the next gallery-app click release needs to be synchronised precisely with the libav transition [15:11] cjwatson, thats what i was referring to (we discussed it in the landing meetings yesterday and today) [15:11] mvo_: you mean this link https://www.youtube.com/watch?v=otCpCn0l4Wo didn't make it obvious enough? [15:12] davmor2: maybe someone should have put that link into the comments field :P [15:12] ogra_: ok, great, what's the plan for that? [15:12] cjwatson, waiting til the transition is over [15:13] oh wait, you said libav [15:13] ogra_: it breaks both ways round; don't we need to make sure to have something ready to go at the same time? [15:13] i was still at exiv2 [15:13] ogra_: damn you beat me too it :) [15:14] ogra_: those two transitions are tangled [15:14] ah k [15:15] ogra_: hence big and complicated and I'm not sure I can predict an exact time [15:15] cjwatson, well afaik we get a new click built every time we merge into trunk ... so its just a matter of making sure to land the click before building the next image after everything got unleached from -proposed [15:15] and to make sure while it is stuck in -proposed that we dont release any click for the app [15:21] sil2100, thanks for the silo, can you binary-copy packages from https://launchpad.net/~phablet-team/+archive/ppa/+packages to the silo? [15:22] oSoMoN: right, I read the comment, let me try that but sadly normally I get evil timeouts always from LP :< [15:22] But let's see, maybe I'll get lucky [15:23] sil2100, do you remember how we did it last time round? [15:23] oSoMoN: I think we found someone that LP likes ;) [15:23] Oh [15:23] Wait, it seems to work this time, let's try [15:23] \o/ [15:23] psivaa, we should get a rerun of the dialer-app tests i think. those results look a bit dodgy [15:26] oSoMoN: hm, the phablet PPA doesn't use the archive builders now does it? Do you remember if we did a binary or source copy last time? [15:26] oSoMoN: is the phablet PPA using -proposed? [15:26] sil2100, last time we did a binary copy, but we did it from a different source PPA [15:27] oSoMoN: ok, sadly we have to do a source copy... [15:27] sil2100, that’s alright [15:27] oSoMoN: since we have to build with -proposed enabled :| [15:27] So it will take some time, sorry about that [15:27] no worries [15:28] sil2100: any silos available? [15:29] bfiller: yes! Line 27, right? mvo_ could you maybe try assigining a silo for Bill? ^ [15:30] sil2100: yes please, line 27 [15:30] mvo_: ^ :) [15:30] done [15:32] brendand: uh, on 119 dialer-app had 6 failures [15:33] brendand: could you take a quickie look? [15:34] sil2100, yeah i can, but i think we should do a rerun. it's all just dbus timeouts, looks like a fluke [15:34] plars: hello! Can we ask for a re-run of the dialer-app AP suite in smoketesting when it's possible? [15:35] sil2100: will do [15:35] Thank you :) [15:35] bfiller, not sure anyone told you ye, but please make sure that no gallery-app click lands until the libav/exiv2 transition lets the gallery-app deb out of -proposed (just a heads up) [15:35] sil2100: mako *just* finished on the smoke tests [15:35] s/ye/yet/ [15:36] Weeeee [15:36] silly dilaer-app :P [15:36] we would be down to 2 failures !!! [15:36] :| [15:36] ogra_: thanks for the heads up, didn't know about that [15:36] davmor2: how's dogfooooodin' goin'? [15:37] bfiller, yeah seems the transition was only half done yet ... landing the click would make it fall over with missing libs [15:37] the rotation init fix made it in it seems, things are looking *way* better [15:38] yep [15:38] brendand and ricmm rock ! [15:39] * brendand bows [15:39] thank you :) [15:39] sil2100: calls, sms, contacts, are good, just doing settings and indicators at the minute then I need to do the hardware tests and then the core apps so far so good [15:40] davmor2: thanks! I guess this image has promotion-potential :8 [15:40] ogra_: ditto camera-app, right? [15:40] oh ? [15:40] * ogra_ didnt notice [15:40] ogra_: that's what the seed comment says anyway [15:40] checking [15:41] well we got a new camera-app ... i'm not even sure thats still valid [15:42] last camera click landed on the 4th [15:42] ah, the transition started on the 5th [15:48] cjwatson, if there is really some dependency on the transitioned libs it is not reflected in the deb dependencies of camera-app [15:48] ogra_: check with ldd? [15:48] but if it doesn't matter, that's good I guess, we should just make sure those seed comments are up to date [15:50] yeah [15:50] ldd doesnt show any direct dep on exiv2 or libav [15:52] sil2100, if it weren't for that stupid dialer_app we'd have just 2 failures! [15:53] sil2100, and i guess uitk is on its way to landing [15:53] brendand: no worries, we'll re-run and ENOBUG [15:53] :> [15:53] lol [15:53] * sil2100 uses firebug to edit the dashboard html, removing the failures [15:54] brendand: what's up with dialer_app? is it the indicator crash or do we still have failures? [15:55] mandel, did the last udm upload add a dependency on lobboost-log ? [15:55] *lib [15:55] ogra_, yes, it was added in the changelog AFAIK [15:55] (trying to find out where the new package comes from) [15:56] mandel, yeah thanks for that === Guest99235 is now known as renato__ [15:56] boiko, i think it's just some issue that happens sometimes where autopilot can't connect to the application [15:56] ogra_, I could have added a better text over "a new dependecy is added" :-/ [15:56] ogra_, sorry [15:57] brendand: ah ok, please let me know if any fix is needed on the dialer-app side [15:57] boiko, of course it could mean the app is not launching properly for some reason, but until/unless we can reproduce it... [15:57] mandel, well it was guessable well enough [15:57] boiko, nothing for now. obviously we'll keep an eye on it and see if the same thing crops up in dialer-app again [15:58] bregma: yep, ok [15:58] mandel, i wasnt sarcastic when saying "thanks" above ;) [15:58] boiko, but it's most likely a random issue that could afflict any app [15:58] ogra_, no no, I got it as a nice comment, but it was indeed to cryptic, will be more clear next time :) [15:58] no worries :) [16:01] sil2100: just found a security concern on the osk need to see if happens elsewhere === Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #113 promoted | CI Train Sheriff: trainguard | Known issues: http://bit.ly/VI2SEl knows your silo status before the spreadsheet does. [16:17] brendand: btw, your py3 MR is approved, I'll ask bfiller to put in the silo together with the other fixes [16:23] can somebody tell me what is happening with the uitk in the silo16 and the qtc plugin in the silo17? Are they stuck somewhere or do they need a kick to move? [16:25] sil2100: Mirv: ^ [16:27] ubuntu-ui-toolkit is in the process of migrating to the release pocket [16:27] so is qtcreator-plugin-ubuntu [16:28] You can see this on https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+publishinghistory and https://launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+publishinghistory [16:30] Not actually sure why it hasn't noticed that silo 16 is done yet ... [16:31] bzoltan: ^- [16:36] oh, I see, ubuntu-ui-toolkit had a newer version landed [16:36] cjwatson: nice, thanks [16:37] sil2100: what should be done with https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/0.1.49+14.10.20140707-0ubuntu1 ? It's newer than the version in silo 16, so citrain hasn't noticed that that's done; is it safe to merge and clean in this circumstance? [16:39] cjwatson: it was Laney who bumped the version for the request from Saviq [16:40] cjwatson, yes, it's safe to merge and clean + ignore_packages_notindest [16:40] That silo is in, so just make the train merge it if you have to [16:40] cjwatson: it is safe to merge as the diff is only the version number and that I will fix when i startthe next landing [16:40] bzoltan: manually merge the MP I proposed [16:40] cjwatson: we can merge & clean it and then just manually merge in the additional changes to trunk [16:46] sil2100: OK, I'll poke that [16:46] Laney: I assume I should do that after the silo16 is merged [16:46] bzoltan: you should be able to do it now, I just merged it === robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #113 promoted | CI Train Sheriff: robru | Known issues: http://bit.ly/VI2SEl knows your silo status before the spreadsheet does. [16:50] sil2100, mvo_, robru : sorry to keep bugging you, still need a silo for line 27 [16:50] bfiller, telephony-service conflicts with silo 9 [16:51] brb o/ [16:51]