/srv/irclogs.ubuntu.com/2015/02/13/#ubuntu-ci-eng.txt

robrubfiller: sorry about that, was on lunch. done00:22
bfillerrobru: cheers, thanks00:28
robrubfiller: you're welcome00:28
robrubfiller: so there's a new thing now: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-018-1-build/ you can get your packaging diffs at build time rather than waiting until the publish step. makes it easier to get packaging reviewed before it's too late00:42
=== chihchun_afk is now known as chihchun
bfillerrobru: cool01:17
cyphermoxrobru: I'm around now?01:18
robrucyphermox: heh, I'm back now ;-)01:18
cyphermoxok01:18
rsalvetibfiller: seeds updated01:37
=== chihchun is now known as chihchun_afk
bfillerrsalveti: thank you02:08
imgbot=== IMAGE 97 DONE (finished: 20150213-03:30) ===03:30
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/97.changes ===03:30
bfillerrobru: mind publishing ubuntu 13 if you're around still?03:36
robrubfiller: yep, was just prepping dinner03:37
bfillerrobru: thanks man, sorry to bug you03:37
robrubfiller: no worries, happy to help03:37
bzoltan_Mirv: do you know what deas that mean? https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-014-1-build/66/console Sounds off in context of the RTM04:41
rsalvetiMirv: nice, qt 5.4 packages are looking good for the emulator05:11
rsalvetinice work05:11
=== chihchun_afk is now known as chihchun
Mirvrsalveti: great news!05:59
Mirvthat means I'll start ushing wih the ~test removed from version numbers06:00
bzoltan_Mirv: I have a strange dependency error in the rtm silo14 withthe gles package06:02
Mirvbzoltan_: "dea"?06:02
Mirvoh, does :)06:03
bzoltan_Mirv:  it looks odd ... specially that Qt is rater stable on RTM ... there was no qt changes there as I know06:04
Mirvbzoltan_: I know I haven't had enough coffee yet, but isn't that dependency error _after_ the source package was already created?06:05
Mirvbzoltan_: as usual, it's not the train but your MP06:14
Mirvbzoltan_: or so I'd think. you have a version number that's bound to raise some eyebrows :D 1.1.1298+15.04.20150212~rtm-0ubuntu1.dsc06:14
MirvI can imagine that causing slight trouble when trying to dput the .dsc file06:14
Mirvwith "as usual" I mean that "CI Train outputs something really strange" usually means "you did something unusual, unless it looks like network is broken on the machines"06:15
bzoltan_Mirv:  I understand that I am  a very stupid person :) But please tell me what did I do wrong?06:27
Mirvbzoltan_: copy-pasting the version number from terminal instead of web browser?06:30
Mirvbzoltan_: so, it's quite visible once you spot it at the first line of https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/rtm-landing-1202-gles/+merge/249560 ...06:31
Mirvit's not that you couldn't have dots in your version number, but CI Train most probably does some cutting based on ".dsc"...06:31
bzoltan_Mirv: OMG... LOL.. sorry...07:00
* bzoltan_ needs coffee07:00
Mirvbzoltan_: hehe07:04
Mirvmandel: are you landing ciborium vivid today? I've also it in my Qt silo (the fix), but I'm glad to remove the MP and just rebuild if you land it08:18
Mirvmardy: could you perhaps review https://code.launchpad.net/~timo-jyrinki/ubuntu-system-settings-online-accounts/fix_qt54_buildfail_new_function/+merge/249069 so I can land it today/Monday with Qt?08:19
seb128Mirv, is new qt planned to land?08:19
Mirvseb128: yes, now that emulator was confirmed to be working and no critical bugs left08:19
seb128Mirv, was settings confirmed to work with it?08:20
Mirv3 bugs overall, one of them is the u-s-s08:20
Mirvseb128: no, the about page bug is still open08:20
seb128since when do we accept that kind of regressions?08:20
Mirvbut I'm stalled because of Kubuntu so landing probably on Monday, not today08:20
mardyMirv: joining a meeting now, I'll get to that in a few minutes08:20
Mirvseb128: well, it's clear it's not hard to fix, FF is approaching, and QA opinion was "no blockers". of course it'd be nice to get it fixed ASAP.08:21
seb128Mirv, you realize that without the about page there is no way to enable developer mode so no way to use adb/connec to the device?08:21
seb128I'm surprised we consider that ok08:21
Mirvseb128: --developer-mode works, but yes the bug could be raised to be Critical08:21
Mirvseb128: maybe one option is to not have that problematic Class usage as a workaround to have the rest of the page working, I can look at that08:22
seb128Mirv, what was the issue again? the move of the storage to qt proper? does that symbol conflict?08:22
Mirvseb128: the move of storage to qt proper without offering QML class anymore (...). maybe you could offer the QML class instead and use it.08:23
Mirvso only C++ is there anymore08:23
seb128Mirv, but we don't update qtsystems, the old one stops working?08:23
Mirvseb128: yes, it does08:23
seb128shrug08:24
seb128well, Laney looked at switching the code to the qt version08:24
seb128but it lacks apis that were in qtsystems and that we need08:24
seb128especially the one to filter storage to list only the internal ones08:24
Mirvthis was probably just the first step in upstream combined with the fact that they didn't support the previous feature.08:25
seb128well, what do we do meanwhile?08:26
seb128if we drop those checks the storage info are going to be wrong08:26
MirvI'd say the feature needs to be reimplemented in our component or offered to upstream qtbase + qtdeclarative for the QML part08:27
Mirvthey won't allow the same class back to qtsystems now that they started on it in qtbase08:27
seb128right08:27
Mirveven if the qtbase lacks features and bindings08:27
seb128but meanwhile what do we do08:27
seb128do we accept wrong storage info as an ok regression?08:27
Mirvhide the storage info temporarily until fix is there?08:27
seb128or do we block the qt5.4 landing on that to be resolved08:28
seb128urg08:28
seb128I didn't follow closely landing rules recently08:28
Mirvthat's alternative, but the push to get 5.4 in is quite big compared to one part of a page08:28
seb128but that seems a world different from previous cycle08:28
seb128where we had "never land with regressions"08:28
seb128now we consider ok to hide main feature from the product?08:28
Mirvwell davmor2 and others from QA could reconsider this and give their thoughts08:29
seb128davmor2, ^ please reconsider08:29
seb128Mirv, also why hasn't that be communicated on eg ubuntu-devel@ list?08:30
seb128it would have helped to give some perspective on the issues and when they need to be resolved08:30
Mirvseb128: usually the bug reporting is enough. the Qt 5.4 plan states it's planned to land before FF, and also there have been e-mails on phablet stating it's coming soon.08:31
Mirvthe bug itself also says "targeted before Feature Freeze Feb 19"08:32
seb128Mirv, yeah, phablet is not a way to reach to everyone is Ubuntu08:32
seb128right08:32
seb128still that seems like a total shift in mindset from the high quality/no regression speech we had for some cycles08:32
seb128we had a time where we were speaking about fixing in some hours or reverting08:33
seb128now we just happily land regressions knowing that things are buggy before even landing08:33
seb128shrug, I should just stop there, I'm going in ranting mode08:33
Mirv:)08:33
seb128I'm going to write an email asking wth happened to the quality standards we preached08:34
ogra_seb128, its friday ... go ahead :)08:34
seb128I'm already annoyed that we have indicator-sound displaying bubbles for nothing every time something happens, and that we didn't revert the buggy upload08:34
seb128I might just go ahead and do that as well, while I'm at it :p08:35
ogra_seb128, i think the issue is that vivid gets less attentiion and everything is handled more loosely since we have RTM with full QA focus08:35
seb128ogra_, well, that's understandable08:35
ogra_the prob here is clearly the lack of manpower in QA08:36
Mirvseb128: we don't have full regression testing in vivid, that's why there are some problems now. Qt 5.4 however has been tested better than probably anything else that's going in to vivid on average.08:36
seb128ogra_, was is less understandable is that we know that e.g qt5.4 landing is going to regress settings and make it impossible to enable dev mode and that we have hand like it was no big deal08:36
ogra_imho we need more communiity involvement on the devel-release side08:36
seb128what*08:36
Mirvseb128: I'm sorry you feel you were left out by not having your bug (about the only one left) considered as critical blocker from the beginning08:36
ogra_yeah, agreed08:36
MirvI felt the bug sounds like easily understandable technical problem instead of risky sounding regression like a crasher would be08:37
seb128Mirv, I don't care much about my bug, but I got handed a devide with qt5.4 the other day and it was a brick to me, I couldn't enable adb and so connect to it to work on it08:37
seb128Mirv, sure is08:37
seb128but still the impact is that it blocks people to do work08:37
seb128no adb, no ssh08:37
seb128how do you even work on a device?08:37
Mirvseb128: yeah the impact needs to mitigated before publishing08:38
seb128well, from what you said that was not going to happen08:38
ogra_no ssh ?08:38
seb128ogra_, we don't install/enable ssh by default do we?08:38
ogra_it is installed by default ... not enabled though08:38
seb128right08:38
seb128so it means a device without dev mode enabled and with a broken UI to access dev mode08:39
seb128what do you do from there?08:39
ogra_you can boot into recovery and set the property to turn ssh on ...08:41
ogra_it will start on next boot08:41
ogra_prob is ... you indeed need working network08:41
seb128yeah, and you need how to do that08:41
ogra_in the normal boot it is /userdata/android-data/property/persist.service.ssh08:41
seb128how many people are going to waste an hour or resolving that?08:41
ogra_needs to have "true" with no newline08:41
seb128that's just wrong, we should fix the known regression before landing08:41
Mirvseb128: we're not going to ship 5.4 with no dev mode in about page08:41
ogra_sure08:41
ogra_just pointing out that there are ways08:42
seb128Mirv, well, sounded like you were about to08:42
ogra_not convenient ones ... but you can always get in somehow08:42
seb128ogra_, yeah, it's just that when you do that you make 15 engineers waste half an hour to resolve the issue and you lost a man-day of work08:42
ogra_sure08:43
Mirvseb128: no, it's just that I'm handling 50+ bugs and 50+ components and I trust upstream to shout too, like you just did. I didn't think the about page is important, but that's because I enabled the dev mode _before_ upgrading to 5.4. I'd be ok though in disabling storage info until you've fixed the core issue, since blocking the whole release on an understood problem could be overkill.08:43
ogra_i didnt say everyone should do it :)08:43
MirvI think that was the QA opinion too, as long as problems are understood they are ok if there are very few of them08:44
seb128Mirv, it's a slippery path, you accept regression/to hide pages, and then everybody forgets about it, and you wake up later with omg vivid quality regressed so much08:44
seb128I though the hard line on no regression was to prevent ending up going that way08:45
Mirvseb128: it's not being forgotten since it's known, unlike some of the other vivid regressions currently in there08:45
Mirvseb128: we can't really not ship 5.4 either, so there's a balancing needed to be done at some poit08:45
seb128right, it's just that we diverge more and more from our goal on quality08:45
seb128it's going to be difficult to get back to the rtm quality if we keep doing that08:45
seb128right08:45
seb128I would expect that the answer to "something really needs to happen" is "the resources are allocated to make it happen", not "ok, we accept to lower quality to get it"08:46
ogra_well, but that means we need someone to put more time into qality on that release ...08:46
ogra_which is really hard if 98% of the QA engineers we have are focused on rtm08:47
Mirvseb128: isn't Laney allocated to it still? surely we can escalate the issue if he doesn't have resources for it, to see what can be done.08:47
seb128Mirv, he is, but he's off today, so I'm unsure he's going to get to it before you land qt5.408:47
ogra_and the remaining 2% need to rush to get anything dones at all to keep up with our devlopment pace08:47
=== chihchun is now known as chihchun_afk
seb128ogra_, well, those are some of the cases where we know things are buggy, no need of QA to point it08:47
seb128it's just a mindset from the landing team08:48
ogra_we need to get away from the 2 distro approach or we need to staff up QA08:48
ogra_there is no requirement for QA testing on vivid silos08:48
ogra_so the QA person testing the image will only see it far after it landed08:49
seb128right08:49
seb128but in this case we know about issues before landing08:49
seb128so we should block landing08:49
ogra_how ?08:49
ogra_no QA person tests the vivid silos08:49
Mirvseb128: I'll look at the bandaid to have most of the page working, and talk with QA what they think of the bandaid08:49
seb128well, we have a bug open saying that settings->about fails to open with qt5.408:49
seb128it has been reported by our landing team08:49
ogra_ah08:50
seb128Mirv, thanks08:50
seb128ogra_, it's just that landing is also happy to sit over and release qt5.4 without fixing the regression, which is what I'm ranting about08:50
ogra_right, that shouldnt have happened08:50
=== chihchun_afk is now known as chihchun
ogra_seb128, and thats what keeps you from adb/ssh ?08:51
seb128ogra_, yeah, no about page, no access to the dev mode switch, no adb08:51
ogra_open the terminal: android-gadget-service enable ssh08:51
Mirvseb128: the opinion was that as long as someone is working on it, it's not a blocker. but I do think not having dev mode is clearly a blocker.08:51
ogra_i thought you have no UI at all08:51
seb128ogra_, assuming you have it installed, which we don't by default on e.g krillin08:52
Mirv(or, not having easy dev mode)08:52
ogra_seb128, the same command above works with s/ssh/adb/ and enables dev mode08:52
seb128ogra_, but yeah, I guess you can install from the store08:52
seb128Mirv, thanks08:52
seb128anyway, enough discussed it08:52
ogra_we talk about vivid08:52
seb128let's try to get the issue resolved08:52
ogra_vivid always has the terminal by default ... wont go away ... even on krillin afaik08:53
davmor2seb128: I'm hoping not to throw petrol on the fire here, but from testing that is the only remaining issue and QT5.4 needs to land before feature freeze and the bug technically isn't one in qt5.4 so I see no reason not to land QT5.4 and09:23
davmor2man my back space skills suck09:23
jibelseb128, another option is to no rely exclusively on manual testing to prevent regression. It is not sustainable. Teams must start by looking at the results of automated tests and fix them. An 80% pass rate on vivid means something http://ci.ubuntu.com/smokeng/vivid/touch/mako/97:20150213:20150210/12295/09:23
davmor2seb128: I'm hoping not to throw petrol on the fire here, but from testing that is the only remaining issue and QT5.4 needs to land before feature freeze and the bug technically isn't one in qt5.4 so I see no reason not to land QT5.4 if it can have a bandaid it will just make it better09:23
jibelseb128, sadly we are not automatically gating on these tests09:24
jibeland talking about system-settings, only 2 tests pass on 12409:29
seb128jibel, yeah, that's an issue09:31
seb128urg, what is the issue with the other ones?09:31
mandelMirv, yes, that is the intention, but if you have it in that silo with the qt fix, can you land yours first, then I'll land mine09:45
mandelMirv, or vice versa, whatever you prefer as long as it lands with the fix (I can reconfigure my silo)09:46
mandelMirv, I think it will be faster on my side that yours09:46
Mirvmandel: yes, please land asap and I'll just rebuild as soon as it's published09:47
mandelMirv, ok, on it09:47
mandelMirv, I have removed the qt mr but either I'm not yet awake or for some reason I cannot reconfigure the silo, can you take a look?09:54
Mirvmandel: hmm, I did actually mean you would land the fix too, so I can rebuild without changes, is that ok?09:54
MirvI always prefer no-change rebuilds09:54
mandelMirv, ok ok, sounds good09:55
Mirvmandel: the only thing is that ciborium needs a rebuild since it uses private headers09:55
Mirvmandel: ok!09:55
mandelMirv, ok, so, let me get this clear, we land my silos with both fixes in rtm and vivid and you keep the mr for qt there so that ciborium is rebuilt because is using the private qt headers due to go-qml, is that correct?09:56
Mirvmandel: 1. rtm wouldn't need 5.4 fix at all, 2. I remove the MP from my landing and do a manual rebuild09:57
Mirv...after your landing with the 5.4 fix is in vivid09:58
mandelMirv, ok, so line 58 is ok atm, correct?09:59
mandelMirv, then, if I find where is rtm silo 000 line, I need to check that one out09:59
mandelMirv, and line 59 should be removed09:59
Mirvmandel: 58 is ok, 59 should be removed unless https://code.launchpad.net/~mandel/ciborium/remount-drives-take-2/+merge/248783 is a critical bug fix targeted to next milestone10:02
Mirvmandel: but it is, so 59 should stay with the rtm version of https://code.launchpad.net/~mandel/ciborium/remount-drives-take-2/+merge/248783 targeted towards rtm branch10:03
Mirvmandel: or, is it that you don't have rtm branch of ciborium, they are identical?10:03
mandelMirv, I think 59 was an error since is pointing to trusty which was an error and in landing-000 rsalveti did the right thing, yet I cannot find the line where he configured it10:04
mandelMirv, so I as saying, 58 ok, 59 out since was an error and we clear that silo, and I try to find where is the line for rtm-00 (google docs sucks at searching)10:04
Mirvmandel: ok, just make sure to fix the critical bug in rtm one way or another, but let's remove 59 for now, and let's land 58.10:05
mandelMirv, +1 to that10:05
Mirv+1!10:06
mandelMirv, can you remove line 59 then? I don't think I have the rights to do it10:09
=== vrruiz_ is now known as rvr
Mirvmandel: yes10:11
Mirvdone10:11
mandelMirv, superb, thx10:12
popeyzbenjamin: what's the chance you can fix bug 1418460? It's blocking a couple of core apps projects.10:12
ubot5bug 1418460 in qtcreator-plugin-ubuntu (Ubuntu) "libconnectivity-qt1-dev un-installable in click chroot" [Undecided,Confirmed] https://launchpad.net/bugs/141846010:12
mandelMirv, testing in vivid atm line 5810:27
zbenjaminpopey: that looks to me like he forgot to add the :armhf suffix10:33
zbenjaminpopey: apt-get install libconnectivity-qt1-dev:armhf10:33
seb128is CI known to be unhappy atm?10:36
seb128settings results on mps look like the application exit on start or something10:36
seb128not sure what's going on10:37
sil2100cihelp: ^ is there any known outage?10:38
seb128e.g https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/1188/10:40
psivaa_seb128: system-settings crash during the AP testing10:44
seb128psivaa_, can we have a bt?10:44
psivaa_seb128: this could be seen in smoke too10:45
psivaa_seb128: http://ci.ubuntu.com/smokeng/vivid/touch/mako/97:20150213:20150210/12295/ubuntu_system_settings/2056866/10:45
psivaa_the crash file is attached there10:45
seb128psivaa_, thanks10:45
psivaa_seb128: np10:45
mandelsil2100, line 74 is syncing from another silo, but yet that is not what we want to do for rtm, removing the stuff under "additional source.." and reconfiguring should be neough, right?10:45
mandelMirv, maybe you know too ^10:46
sil2100mandel: yeah10:49
mandelsil2100, sweet, thx10:49
mandelsil2100, I wanted to be 100% sure10:49
sil2100mandel: although we might need to remove the packakages by hand from the PPA itself10:50
sil2100Not sure if the new build job is fixed in regards of that10:50
mandelsil2100, ok, I''ll try and we'll see10:50
Mirvdavmor2: seb128: there is u-s-s bandaid now in the PPA tested to be working - storage info commented out, all other parts work. Laney has another branch that I'll take a look which may bring us initially "storage info is there, but not yet correct"11:00
Laneyno11:00
Mirvok, so not bringing that11:01
Laneyyou might need to combine, my commit only gets the free space calculation working11:01
Mirvoh, ok. well, I'll look at it.11:01
Laneyit's a problem because they removed this storageType thing >:(11:01
Laneyso one other bandaid is to copy that function somewhere11:01
davmor2Laney, Mirv: the one important question is this, can you enable developer mode and reset the device?  As far as I am concerned those 2 items are the critical ones on the about page, Anything above that is a bonus for a bandaid till the full fix is in :)11:03
davmor2Laney, Mirv:  I'm assuming it will be longwinded but minor fixes to get everything else up and running right?11:04
Mirvdavmor2: I tested developer mode, testing reset too although I assume it doesn't use much Qt functionality what it's doing11:05
Mirvdavmor2: yes so the current bandaid is purely commenting out two sections in QML http://pastebin.ubuntu.com/10202733/11:05
Mirvso that the rest of the page that doesn't use removed Qt features can load11:06
Mirvdavmor2: so your usual about page sanity test is to switch developer mode + use reset?11:07
Laneyif you take my commit I think you'll be able to have the storage item there but you should make it un clickable11:07
Laneyi.e. just turn off Storage.qml11:07
Mirvok Laney11:07
Laneybut try it11:07
Mirvtrying11:07
Laneynot sure I got as far as test building11:07
Laney;-)11:07
davmor2Mirv: For sanity testing I just need to enable developer mode for the upgrade test, in the regression testing though it is deeper.   But it is good to know that they both work for that.  :)11:08
Mirvyeah reset seems to have worked, back to the wizard now11:08
* sil2100 off to lunch11:43
=== marcusto_ is now known as marcustomlinson
MirvLaney: seb128: made laney's branch a WIP MP and commented what I needed to do to get the portion of the functionality back: https://code.launchpad.net/~laney/ubuntu-system-settings/storageinfo-5.4/+merge/24963012:11
Mirvcombined with only a single commenting out of the StorageInfo in the qml file this time12:12
Mirvso the free space count is back12:12
rsalvetimandel: hey, trying to understand the landing then12:17
rsalvetimandel: we got a ciborium one for vivid and rtm12:17
rsalvetimandel: are you landing the vivid one now?12:17
rsalvetimandel: and also, are we ready to set the rtm one to needs qa?12:17
rsalvetiMirv: great, just let me know when you rebuild your packages again (removing the ~test)12:27
rsalvetiso we can give another round of testing12:27
Mirvrsalveti: it's done already, but Kubuntu is keeping us back so I'll wait for Monday anyhow12:28
Mirvthere are no changes in any package other than the version string change in changelog12:29
rsalvetiMirv: oh, great then12:32
Mirvmandel: thanks, I'll rebuild it in the 5.4 PPA after that12:37
mandelrsalveti, yes, I'm going to test the rtm now and will set it ready for Qa to land12:47
rsalvetimandel: great, and for vivid? can't we just land it now?12:48
rvrbfiller: boiko: ping12:48
mandelrsalveti, yes,  but we need to coordinate with Mirv AFAIK is ok, is that correct?12:48
Mirvmandel: rsalveti: I landed it already and rebuild is ongoing in the Qt 5.4 PPA12:49
mandelperfect12:49
Mirvsince you marked it as tested12:49
mandelMirv, yes, it was tested12:49
rvrbfiller: boiko: I'm testing silo 11. Taking a look to the silo diff, there is a change to factory-wipe.conf12:50
rvrbfiller: boiko: Line 69 https://pastebin.canonical.com/125629/12:50
rvrbfiller: boiko: Can you confirm or deny?12:51
rsalvetimandel: Mirv: even better12:51
mandelrsalveti, I'm testing in rtm ciborium and will set it ready for qa in a few mins12:52
mvohm, the citrain gives me a hard time assigning #92 (click). I get a fatal error12:54
boikorvr: checking13:00
boikorvr: hmm, that doesn't seem right13:01
boikorvr: bfiller: it looks like something landed on rtm and was not committed to bzr13:01
rsalvetimandel: thanks13:02
rvrboiko: I'm using citrain-diff tool by brendand13:02
=== alan_g is now known as alan_g|lunch
rvrboiko: Do you think the diff is right?13:02
boikorvr: so, the diff for ubuntu-touch-session should only contain this: https://code.launchpad.net/~tiagosh/ubuntu-touch-session/rtm-14.09-fix-1413316/+merge/24923013:03
boikorvr: it seems the ubuntu-touch-session RTM bzr branch is outdated13:04
rvrboiko: As far as I remember, factory_wipe fix was done via device tarball, can that explain it?13:05
boikorvr: yep, that probably explains it13:07
boikorvr: let me compare the commit history with the changelog, just a sec13:07
mvohey trainguards, I have trouble assigning a silo for #92 (new click release). am I doing something wrong?13:10
mvoI got this: https://ci-train.ubuntu.com/job/prepare-silo/4098/13:10
mvo2015-02-13 12:58:25,797 ERROR Could not find REQUEST_ID 1423832036072 in any silo.13:10
mandelrsalveti, set to be tested by QA13:11
boikorvr: yep, ricmm's changes are not in bzr, we need to sync that somehow13:12
boikorvr: I mean, before landing silo 1113:12
rsalvetimandel: awesome13:12
mandelrsalveti, dealing with the udm stuff to get it landed today too13:12
rsalvetimandel: cool13:13
rsalvetilanding day13:13
boikorvr: I'll go for lunch now, but right after I'm back I will deal with that, ok?13:14
rvrboiko: Ok13:20
tvoss_trainguards, can I get a silo for line 93?13:23
=== MacSlow is now known as MacSlow|lunch
=== chihchun is now known as chihchun_afk
jibelsil2100, testing report sent. Same pass rate than previous run with more tests executed.13:29
sil2100jibel: o/13:42
sil2100Thanks!13:42
sil2100tvoss_: on it13:42
tvoss_sil2100, thx13:43
=== alan_g|lunch is now known as alan_g
sil2100jibel, john-mcaleely, ogra_, pmcgowan: so it seems we're green on promoting 234 to the rc channel13:49
sil2100The only problem I see now is...13:49
john-mcaleelyuhoh13:49
sil2100The idea was to promote those 2-week images to the ubuntu-touch/rc/bq-aquaris.en channel, but what about the emulator and mako images?13:50
sil2100I mean, we could have those in that channel too13:50
sil2100But the name indicates 'bq-aquaris.en' - so I doubt anyone would actually see or use those images on mako13:50
sil2100;)13:50
sil2100Since who would flash their mako with an aquaris channel?13:50
john-mcaleelyhm. maybe we need a 14.09/rc ?13:50
sil2100Yeah, what I would propose is creating an alias to the aquaris channel13:51
pmcgowanso I will defer to john-mcaleely  but we do not want the ota going to krillins in the field yet13:51
sil2100I know it's a bit dirty, but would work for sure13:51
john-mcaleelysil2100, definately a bit dirty, but sure, why not13:52
john-mcaleelypmcgowan, yeah, it's all fine so long as we stay out of stable/13:52
john-mcaleelyand having a more generic name for people to flash makos from seems good13:53
pmcgowannot sure we need another channel, folks can use proposed or wait?13:54
ogra_sil2100, i would just leave these arches out13:54
pmcgowanno one using stable would flash a special channel13:54
john-mcaleelyisn't it a bit unfair to the mako folks?13:54
pmcgowanI suspect few mako stable users?13:55
john-mcaleelybut sure, mako is a dev tool, so stable or proposed might be all you need13:55
john-mcaleelyindeed13:55
john-mcaleelydo we need it for test coverage (ie only mako exercises some areas?)13:55
sil2100We could leave them out, sure, but it does seem to be a little bit of a waste13:56
pmcgowandont think so, since mako has less stuff than krillin13:56
Mirvsil2100: robru: help! I removed ciborium MP from 005 and replaced it with manual upload to do a simple rebuild now that ciborium landed from another silo, and build job is failing https://ci-train.ubuntu.com/job/ubuntu-landing-005-1-build/108/console - I'd need fully succeeding build run of 005 (and publish later on) by Monday13:56
bfillerboiko: can you check with rsalveti or ricmm on that? looks like ubuntu-touch-session may have been sycned from vivid and the rtm branch not updated? maybe we should just be re-syncing if that is the case?13:56
Mirvso I think it has a bit somewhere that tracks the now obsolete MP related build number13:57
sil2100Mirv: uh oh! Might be something with the new build job, let me dive into that but robru would be the best person to poke13:57
john-mcaleelyFor me, this would be for an stable/ mako community of non-devs13:57
john-mcaleelyprobably very small, but perhaps important?13:57
Mirvsil2100: robru: this is also a situation that may not have happened before - removing MP and replacing it straight away with manual upload. I could workaround it of course by doing empty MP instead.13:58
Mirvsil2100: robru: because usually train packages are of course handled via MP:s, but the empty MP:s did not work too well in one previous Qt landing so I've chosen this track plus manual syncing of certain trunks instead13:58
sil2100Mirv: but I remember we allowed things like that before at least13:59
Mirvsil2100: it clearly remembers it used to do a build of ciborium from MP with a certain bumped version number, and is now confused since there's another direct upload instead13:59
sil2100A reconfigure should wipe his .project file in the normal case and re-create it, but let me check how it's right now14:03
Mirvsil2100: I reconfigured (via prepare-silo) the silo after removing MP + adding manual source14:09
jdstrandhey-- I'm on 14.09-proposed r194 mako and over the last two days I saw some bad behavior that I haven't seen in months and months14:11
jdstrandspecifically, twice I had to reboot my phone because side edge gestures didn't work. I could swipe from the top for notifications, and swipe from the bottom to hide that, but I could not swipe from the left to reveal the launcher or from the right to switch apps14:12
mvohey trainguards, I have trouble assigning a silo for #92 (new click release). am I doing something wrong?14:13
mvo(sorry for re-asking, my network was down for some minutes)14:13
jdstrandhas anyone seen this?14:13
* jdstrand didn't see it mentioned on the list14:13
jdstrandlooking at http://people.canonical.com/~ogra/touch-image-stats/rtm/, it is not immediately obvious what might've changed14:16
jdstrandthat might cause this14:16
ogra_you need to map the mako version against krillin14:16
ogra_the rtm changelogs above are all against krillin version numbers14:17
* jdstrand just went by the date14:17
ogra_ah, k14:17
ogra_yeah, that should be fine14:17
jdstrandwent back for the last 5 changes14:17
jdstrandmaybe I'll do all of Feb just to be tidy14:18
sil2100mvo: hey!14:18
sil2100mvo: let me look14:18
sil2100mvo: hmm, #92 doesn't seem to look like your landing, can you refresh the spreadsheet?14:19
sil2100mvo: I think it might be bugged on your side and it didn't register you entering the details14:19
sil2100ogra_, jibel, pmcgowan, john-mcaleely: so for now I'll promote 234 to the rc channel for krillin and wait for Steve with the rest of the devices14:20
rvrmandel: Silo 0 has no associated bug in the spreadsheet14:20
kenvandinejgdx, i kicked a rebuild of silo 15 because we've had a bunch of landings since that14:20
john-mcaleelysil2100, ac14:21
john-mcaleelyk14:21
ogra_sil2100, +114:21
jgdxkenvandine, thanks14:22
kenvandinejgdx, so what's the status of that stuff?  have we nailed down the issues found in the rtm silo?14:22
kenvandinejgdx, sorry i haven't been following it lately14:22
pmcgowanjdstrand, there is an open bug for edges not working, I have seen it14:22
jdstrandpmcgowan: ah, good to know14:23
pmcgowanjdstrand, if you have more info https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/140826314:24
ubot5Launchpad bug 1408263 in android (Ubuntu) "Edge gestures still get lost" [Undecided,New]14:24
jgdxkenvandine, it's blocked by https://bugs.launchpad.net/barajas/+bug/137877814:25
ubot5Error: launchpad bug 1378778 not found14:25
* jgdx adds that to spreadsheet14:25
jdstrandpmcgowan: that's it exactly. I'll subscribe and see if I can help with more info14:25
jgdxkenvandine, ah- sorry. Bit late14:26
pmcgowanjdstrand, and I have had them come back without a reboot, quite odd14:26
kenvandinejgdx, ah, bummer... so it's blocked by another bug :/14:26
mvosil2100: ok, let me try again with a different browser14:29
jdstrandpmcgowan: no reboot, that is odd. though in the moment I want to use the phone, I really want to use it (both cases needed to make a call)14:29
pmcgowanjdstrand, same, I launched dialer from the app scope to get to it, then after the call edges worked14:31
jdstrandyeah, unfortunately I didn't have the app scope up14:32
jdstrandI had the music player once and something else the other time (I don't remember)14:32
bzoltan_mvo:  I subscribed to your landing and I will help it with running the SDK's functional tests too14:33
mvosil2100: indeed, none of the information I put there was there its there now (I think) in line #95 but still no cookie, i.e. I still get a jenkins error when I try to start the build14:33
mvosil2100: eh, I mean when I try to assign a silo14:33
sil2100mvo: let me try it then14:33
sil2100mvo: it's for vivid, right? As the series wasn't assigned14:33
mvooh, geeh14:33
mvosorry14:33
* mvo feels a bit silly now14:34
sil2100mvo: assigning :) No worries!14:34
sil2100ubuntu/landing-013 for you14:34
mvo\o/14:34
sil2100=== IMAGE rc.RTM #18 promoted ===14:37
sil2100(krillin #234, only to the rc channel)14:37
sil2100(images mako #194 and generic_x86 #188 wait for additional decision-making)14:38
john-mcaleelydownloading and updating on my handset14:44
john-mcaleelyI wonder if I'm the only user of that channel :-)14:44
john-mcaleelythanks sil210014:44
sil2100Mirv: ok, digging deeper into your issue now, it seems the train didn't change the .project file, which is probably something that it should do ;p14:44
sil2100john-mcaleely: \o/ I might use it as well, but since I reflash my device like crazy between rtm and vivid, I guess I wouldn't really feel any merits of using this channel ;)14:45
john-mcaleelyheh14:46
sil2100jibel, davmor2: thanks for the testing guys!14:46
john-mcaleely+114:46
sil2100Mirv: I think there might be a small misconception regarding handling of the additional source uploads indeed14:47
sil2100pstolowski: oh, your landing seems to have found a small issue in our new build job ;)14:49
sil2100pstolowski: I'll be publishing as I suppose train-related uploads saw worse things, but it seems the train currently doesn't trim down the commit-message to the first newline14:49
sil2100Anyway, publishing14:50
Mirvsil2100: can the .project file be manually changed or should I simply opt for empty MP to get back on track?14:53
pstolowskisil2100, ah.. what was that? the remark about no abi breakage made in the commit msg?14:53
Saviqelopio, could we ask you for a review of https://code.launchpad.net/~josharenson/unity8/screenshot_ap_test/+merge/249542 please? :)15:00
elopioSaviq: of course. I'm on it.15:00
sil2100Mirv: I could hack the .project file, but maybe a cleaner way would be to include an empty MP for now, if that's fine with you of course15:02
sil2100Mirv: since I see the problem is that when a build is started as watch_only, all the steps that potentially re-generate the .project file are skipped15:03
Mirvsil2100: robru: empty MP for this one is ok to me15:04
=== MacSlow|lunch is now known as MacSlow
Saviqtrainguards, silo for line 96 please :)15:05
sil2100Saviq: o/15:07
=== sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Big changes in CI Train build job, ping robru at the first sign of trouble.
=== sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Big changes in CI Train build job, ping robru at the first sign of trouble. Ubuntu-RTM landing gates closed.
boikotrainguards: can I please get a reconfigure on vivid silo 007?15:15
sil2100boiko: sure, what changed?15:15
boikosil2100: I added a new component (address-book-app) there15:15
sil2100Ah, new component, on it15:15
boikosil2100: yep :)15:16
sil2100boiko: should be good :)15:16
boikosil2100: thanks!15:17
Saviqsil2100, sorries, can have reconfigure for vivid silo 18, somehow managed to miss a project+MP15:23
sil2100Saviq: sure thing15:23
sil2100Saviq: done15:25
Saviqsil2100, thanks15:29
Saviqohnoes :?15:31
boikorvr: where can I get that script that generates the packaging diff? I want to make sure it is ok now15:32
rvrboiko: One moment15:32
rvrboiko: https://code.launchpad.net/~brendan-donegan/phablet-tools/citrain-diff15:33
rvrboiko: http://bazaar.launchpad.net/~brendan-donegan/phablet-tools/citrain-diff/view/head:/citrain-diff15:33
boikorvr: nice! thanks!15:34
plarskenvandine: regarding the system-settings ci issue, talking to fginther about it now so I wanted to move here...15:38
plarskenvandine: how are you running it when you try it locally? are you using phablet-test-run? That's all we do in CI15:38
plarsso assuming you are running it the same way, we struggle to find anything that's different15:38
kenvandineyeah, phablet-test-run15:39
boikorvr: I am doing a last test on silo 11, but the diff looks ok now at least15:39
kenvandineplars, i thought in CI there was a script run that does a bunch of restarts?15:39
kenvandineso it's a little different15:39
plarskenvandine: restarts?15:39
rvrboiko: Did you change anything?15:39
kenvandinemaybe that's just smoke tests?15:40
kenvandinesomething that restarts the device between tests15:40
kenvandineit seemed much more complicated that just phablet-test-run on the whole thing15:40
plarskenvandine: the CI scripts for smoke and ci all just use the standard phablet tools for provisioning the device (ubuntu-device-flash), setting it up and running it15:40
kenvandinephablet-test-run -r 0000 ubuntu_system_settings15:41
kenvandineis all i did15:41
plarskenvandine: ah, right in smoke we reboot between test suites. But it's still just phablet-test-run each time15:41
kenvandinedoes that happen in CI too?15:41
kenvandineor just smoke?15:41
plarskenvandine: well it's just running one suite in ci, so no reboot between because there is no between15:42
kenvandineok15:42
kenvandinei didn't flash my device right before15:42
kenvandinewhich i don't want to do on a friday, my mako is my daily driver right now :)15:42
plarskenvandine: well that's something we do differently15:42
fgintherkenvandine, when running MP tests, there is a specific script that can be used: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/README-cli.rst#L8115:43
plarskenvandine: we always provision before and start with a fresh environment15:43
fgintherkenvandine, I have a mako sitting here unused, I can give try to reproduce it locally15:43
kenvandinefginther, i'd appreciate it15:43
Saviqsil2100, aah, build job rewrote the silo metadata, please reconfigure again15:44
kenvandinewe'd really like to figure out what caused it to start failing15:44
kenvandineit was reliable for weeks...15:44
fgintherkenvandine, I'll let you know the results, at least try to make sure the problem is specific to a set of devices15:44
fginthererr, s/is specific/is not specific/15:44
rvrboiko: bfiller: Approving silo 9.15:44
bfillerrvr: thanks15:45
boikorvr: thanks, as soon as it lands I can rebuild silo 1115:45
=== sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Big changes in CI Train build job, ping robru at the first sign of trouble.
sil2100davmor2, jibel: if we could get someone signing-off the oxide landing today it would be a very nice thing, since it would give us the whole weekend of dogfooding texting15:59
sil2100s/texting/testing15:59
sil2100It might be abit too much for QA in our TZ, but maybe it could be handed off to ToyKeeper somehow?16:00
jibelsil2100, davmor2 is on it but it's huge.16:00
bzoltan_Mirv: ^ what the hack is that?16:07
om26erbzoltan_, Hey!16:14
sil2100bzoltan_: uh oh, is that during build time?16:15
rhuddieboiko, I am testing silo 3, dialer-app autopilot tests. which tests should be fixed by this silo? I am seeing 4 failures.16:17
sil2100bzoltan_: hmmm, where does this message come from actually? Am I blind or did the build actually succeed?16:19
boikorhuddie: you see 4 failures with the silo or without it?16:19
rhuddieboiko, both.16:19
boikorhuddie: it was supposed to fix all failures, mind providing me some logs with the failures so that I check them?16:20
rhuddieboiko, here are the logs. I've just copied the call stacks: http://pastebin.ubuntu.com/10206746/16:24
Saviqsil2100, I'll need another reconfigure of vivid silo 18 please, the train rewrote the config, 'cause was building already...16:29
Saviqalso, trainguards, I can has silo for line 97 please16:29
sil2100ogra_, jibel, davmor2, popey, robru: I might be a bit late for the meeting since I need to fetch my girl from the train station16:29
sil2100Saviq: assigned, now reconfiguring16:30
Saviqsil2100, faster than light!16:30
bfillersil2100: can you publish rtm 9 please?16:32
rsalvetidavmor2: jhodapp: kgunn: sil2100: https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/142172116:46
ubot5Launchpad bug 1421721 in mediaplayer-app (Ubuntu) "Can't open mediaplayer-app anymore on vivid 97" [Critical,Confirmed]16:46
rsalvetiwill check with some older images now16:46
jhodapprsalveti, cool thanks16:46
slangasekis proposed-migration in place for 14.09-factory{-proposed,}, like it is for 14.09? wgrant, infinity, cjwatson?16:50
cjwatsonslangasek: yes16:51
slangasekcjwatson: great, thanks16:52
cjwatsonslangasek: http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/ has the output16:52
popeyzbenjamin: on a different pc than the one I usually use, I'm getting "Unable to find a shell" when I maintain my kit. We have seen this before haven't we?16:55
sil2100Ok, made it on time16:55
ogra_<Saviq> sil2100, faster than light!16:56
ogra_:D16:56
kgunntrainguards hey there, could i get a reconfig on vivid silo 016:56
sil2100kgunn: on it16:56
sil2100bfiller: on it too!16:56
boikorhuddie: ok, I will have to work on those, two of them I don't really know why they happen (the second and the third errors), but the other two I have seen happening once, I will work on those17:06
rhuddieboiko, alright thanks.17:07
=== ChickenCutlass is now known as ChickenCutlass_a
=== ChickenCutlass_a is now known as ChickenCutlass
=== ChickenCutlass is now known as ChickenCutlass_a
om26eralexabreu, Hi!17:21
alexabreuom26er, hey17:21
om26eralexabreu, I have verified the fix in silo15. what part of the TestPlan I need to run ?17:21
om26erthe testplan seems a bit different than most projects17:21
alexabreuom26er, only the 2 first bits (cordova is not related)17:22
om26eralexabreu, hmm, ok. So nothing to test on the device except to make sure apps start fine ?17:23
alexabreuom26er, mmh the TP can be expanded a bit (I'll do it), but otherwise yeah17:25
om26eralexabreu, it'll be helpful if you add a testcase for the bug fix in the silo.17:29
alexabreuom26er, it is there already, just running on the device didn't workw/o the fix17:31
rsalvetijhodapp: image 96 is fine17:35
jhodapprsalveti, wow, so it broke just with 9717:36
rsalvetijhodapp: yeah17:36
jhodapprsalveti, got a link to what changed? I never know how to find that lol17:36
rsalvetijhodapp: there was a mediaplayer-app update17:36
rsalvetijhodapp: just updated the bug17:36
jhodappoh really17:36
jhodapprsalveti, who committed it that we should talk to?17:37
rsalvetijhodapp: https://launchpad.net/ubuntu/+source/mediaplayer-app/0.20.5+15.04.20150213-0ubuntu117:37
rsalvetibut need to update it from 96 and see17:37
rsalvetiwill do that in a minute17:37
jhodappk17:37
alexabreuom26er, I added 2 test cases if you want to run them17:41
om26eralexabreu, yes, I am in the process of setting up QtCreator.17:42
charlestrainguards, line 62 (rtm silo 19) is in error, the wrong MPs were pasted into the spreadsheet. can they be cleared out and I'll redo17:46
robrucharles: yeah just make sure the right MPs are in there and I'll update the silo.17:47
charlesrobru, ack17:47
bzoltan_om26er: who did you ping about that RTM branch?17:48
om26erbzoltan_, I pinged about silo 1417:48
bzoltan_om26er:  who did you ping?17:48
om26erbzoltan_, I pinged you17:49
om26erbzoltan_, I just wanted to know wanted to know is how do I verify the fix ? seems related to translations17:50
bzoltan_om26er: "No response from the Devs regarding a way to verify the fix. " != "Hey" :)17:50
om26erbzoltan_, Yeah, I had to put in a reason for why I was not testing that silo. Perhaps bad use of words from me.17:51
bzoltan_om26er:  I think you could go ahead and valiate the sile from the point of regression and general functionality check. Pete Woods and Andrew Hayzen  are the folks who should make the call based on this - https://bugs.launchpad.net/ubuntu-translations/+bug/132741917:55
ubot5Launchpad bug 1327419 in libusermetrics (Ubuntu) "Infographic's language not updated until the metric value is changed" [High,In progress]17:55
fgintherkenvandine, I ran the tests for the packages associated with https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/982/testReport/junit/ubuntu_system_settings.tests.test_security/SecurityTestCase/test_locking_control_value/17:55
fgintherkenvandine, I saw 109 failures when useing "phablet-test-run -r 0000 ubuntu_system_settings" and a few more using the run-mp script17:56
fgintherkenvandine, Most of the failures log the message "Appears process has already exited"17:57
kenvandinefginther, humm... do you have python3-evdev installed?17:57
kenvandineat one point that wasn't getting installed as a dep17:57
kenvandinebut that'll cause that number of failures17:57
fgintherpython-evdev is installed17:57
kenvandinepython3-evdev?17:58
fgintheroops, yes that too:17:58
kenvandinehmm17:58
fgintherpython3-evdev:17:58
fginther  Installed: 0.4.1-0ubuntu317:58
kenvandinedunno17:58
kenvandinesomething's wrong there :)17:58
kenvandinethat's worse than what happens in CI :)17:59
=== alan_g is now known as alan_g|EOW
bzoltan_om26er: and if you would have checked the MR you could have seen that it is covered with unit tests -> https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/i18ntagRTM/+merge/24935718:01
om26erbzoltan_, sure, I'll do that. I am testing a silo, which take a few minutes.18:01
om26erbzoltan_, yeah, I saw the MR.18:02
bzoltan_om26er:  and the unit test results are available in the build logs -> https://launchpadlibrarian.net/197449045/buildlog_ubuntu-rtm-14.09-armhf.ubuntu-ui-toolkit_1.1.1298%2B15.04.20150212~rtm-0ubuntu1_UPLOADING.txt.gz18:02
bzoltan_om26er:  look for "tst_i18n: ********* Start testing of tst_I18n *********"18:02
om26erbzoltan_, thanks for the link. So I guess I'll just work on general checking around things for regressions.18:04
bzoltan_om26er:  But fundamentally I would love to see pete-woods's ack on the implementation. He was requesting that feature as dependency for fixing the #132741918:04
om26erbug 132741918:05
ubot5bug 1327419 in libusermetrics (Ubuntu) "Infographic's language not updated until the metric value is changed" [High,In progress] https://launchpad.net/bugs/132741918:05
om26er_mup_ is missing.18:05
bzoltan_om26er: :) well, do not be soft on us. Give your most critical eyes ... it is an OTA release. Serious stuff.18:05
om26erSounds like military training :D18:06
fgintherkenvandine, let us know if there is any more info we could provide. At this time, the issues appears to be outside of how the test is being executed, so I'll leave it in your hands.18:07
kenvandinefginther, ok, thanks for trying18:07
kenvandinefginther, at least it works better in CI than it does on your device :)18:07
fgintherkenvandine, the last two image tests don't look much better though :-( http://ci.ubuntu.com/smokeng/vivid/touch/mako/97:20150213:20150210/12295/ubuntu_system_settings/18:08
kenvandinefginther, could you try it one more time with what's in vivid?18:08
kenvandineoh my18:08
fgintherkenvandine, do you mean just a standard image, no MPS?18:08
kenvandineyeah18:08
fgintherkenvandine, sure18:09
kenvandinethx18:09
kenvandinethat's what i was running the other day18:09
kenvandinefginther, the smoke test does include a crash file18:11
kenvandinejgdx, the smoke testing crash file shows that haptic feedback stuff too18:12
robrusil2100: what's up with rtm landings? ^18:15
robrucan I land stuff? I thought gates were closed18:15
sil2100robru: yeah :)18:15
sil2100robru: as per topic, all is good, we're open18:15
robrusil2100: ok thanks18:16
davmor2sil2100, dbarth: oxide-qt passes all day and 2 minor issues, one of which is the ebay site itself and the other looks like it is a weather app issue \o/18:16
robrucharles: oh sorry, did you put the right MPs in row 62 yet?18:17
=== robru changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: -
kenvandinefginther, the smoke testing took a dive between the 10th and 12th18:20
kenvandinefginther, 90.9% pass on the 10th18:20
kenvandineand 6.3% on the 12th18:20
om26eralexabreu, Hey18:21
alexabreuom26er, hey18:21
charlesrobru, not yet, looks like ubuntu-themes didn't have an rtm branch yet so I'm setting that up18:21
om26eralexabreu, since I installed the silo on the device, I wonder why am I testing the Ubuntu SDK ?18:21
robrucharles: ah ok, just ping me when you're ready then18:21
fgintherkenvandine, it looks like there was a new version of ubuntu-system-settings, 0.3+15.04.20150211.1-0ubuntu1. But not sure if that coincides to the failures18:21
kenvandinethe failures seem to be low in the stack18:22
kenvandineall starting with haptic feedback stuff18:22
kenvandineso i suspect one of the qt packages18:22
om26eralexabreu, also "Run HTML5 Application on Device" is greyed out due to some reason.18:22
alexabreuom26er, mmh not sure I get what you are saying, ... you are testing html5 apps, making sure that they run properly18:22
kenvandinewhich image 96 on the 12th had a bunch of qt related packages18:22
kenvandineand mir18:22
kenvandineetc18:22
alexabreuom26er, the TP needs an update, the option has been removed (and included in the usual "run")18:23
kenvandinejgdx, interesting, one thing that landed between the good smoke tests and bad smoke tests is the other vibrate branch18:24
kenvandinejgdx, which is hidden, so not even shown18:24
kenvandinebut the crashes all seem to stem from haptic feedback related stuff18:25
kenvandinehuge list of changes in image 96 http://people.canonical.com/~ogra/touch-image-stats/96.changes18:27
kenvandinethe pass rate went from 90.9% in #95 to 6.3% in #9618:29
om26eralexabreu, when I run it, it always executes the app on the desktop18:30
om26ereven I have my phone connected with adb enabled18:30
alexabreuom26er, you have to change the kit, and select the one associated w/ the device18:30
sil2100kenvandine: remember you can have changes with CI Train landing descriptions in http://people.canonical.com/~lzemczak/landing-team/ubuntu/vivid/96.commitlog18:31
om26eralexabreu, "there is currently no kit defined for your device"18:31
kenvandinesil2100, right, thanks!18:31
om26erI tried 'Autocreate' button that gives an error18:31
alexabreuom26er, go to the project> tab on the left and add one (Add kit)18:31
alexabreuom26er, if you need to create one, go to the device tab and click on the device connected and there is a way to create a kit for it18:32
jhodapprsalveti, I bet it was revision 326 and 328 that broke mediaplayer-app: http://bazaar.launchpad.net/~phablet-team/mediaplayer-app/trunk/revision/32618:34
jhodapphttp://bazaar.launchpad.net/~phablet-team/mediaplayer-app/trunk/revision/32818:34
rsalvetijhodapp: I noticed we're missing one package in this image18:34
rsalvetijhodapp: qtdeclarative5-ubuntu-ui-extras0.218:34
jhodapprsalveti, which one?18:34
rsalvetijhodapp: the image was built before the new seeds got published18:35
jhodapprsalveti, well those changes supposedly remove the need for that package, so that's probably why it was removed18:35
jhodapprsalveti, ah, that's probably why then18:35
rsalvetiright, but then bill requested qtdeclarative5-ubuntu-ui-extras0.2 to be included in the seeds18:35
rsalvetibut still didn't try18:35
rsalvetijhodapp: doing apt-get update/upgrade now and will see18:36
jhodapprsalveti, ok, interesting that it requires qtdeclarative5-ubuntu-ui-extras0.2 but I don't see an include in the VideoPlayer.qml for that version18:36
rsalvetijhodapp: right18:36
rsalvetiprobably a bug indeed18:36
rsalvetibfiller: ^18:36
rsalvetijhodapp: but worked fine after apt-get update/upgrade18:37
rsalvetijhodapp: going to trigger a new image18:37
jhodappoh really18:37
jhodappnice18:37
rsalvetihm, http://iso.qa.ubuntu.com/qatracker/milestones/326/builds says rebuilding but I don't see that yet in https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/18:37
rsalvetibut should show up soon18:37
kenvandinejhodapp, bfiller had said he missed an import that needed to be removed, in mediaplayer18:37
kenvandineand had a fix pending for it18:37
jhodappkenvandine, I see that as revision 328 for mediaplayer-app18:38
jhodappkenvandine, so he was saying it just hasn't landed?18:38
bfillerrsalveti: it's fixed in new mediaplayer-app18:38
kenvandineyeah18:38
kenvandinei missed it in this first branch18:38
rsalvetibfiller: great18:39
bfillerjhodapp, rsalveti : should be in next image, just apt-get install it18:39
jhodappbfiller, so the fix is to just remove the qtdeclarative5-ubuntu-ui-extras0.1 dependency right, doesn't it require qtdeclarative5-ubuntu-ui-extras0.2 though?18:39
kenvandinersalveti, we still need the image with the seed change though :)18:39
bfillerjhodapp: no18:39
rsalvetikenvandine: the seeds was changed already18:39
kenvandinersalveti, yeah, but no images since18:39
rsalvetistarted a new one, waiting now :-)18:39
bfillerjhodapp: mediaplayer-app doesn't rely on extras at all anymore but you need the latest version of it18:39
kenvandinersalveti, thanks!18:40
jhodappbfiller, ok18:40
bfillerjhodapp: the fixed version of mediaplayer-app has landed but just not in the image yet18:41
alexabreutrainguards can you reconfigure RTM silo13  pls?18:41
jhodappbfiller, makes sense, thanks18:41
rsalvetijhodapp: next image should be all good then18:47
jhodapprsalveti, yeah, confirmed that it's working after an upgrade18:47
om26eralexabreu, I see this error when starting the app: http://i.imgur.com/hTlsspB.png18:48
rsalvetijhodapp: great18:48
jhodapprsalveti, testing silo 1718:48
om26eralexabreu, am I using wrong version of Ubuntu or something18:48
rsalvetijhodapp: cool18:48
jhodapprsalveti, is anyone debugging the vivid hanging issues?18:48
alexabreuom26er, mmmh you should be using the ubuntu-sdk-14.10 sdk18:49
rsalvetijhodapp: will jump on that later today I hope18:49
robrualexabreu: on it18:49
jhodapprsalveti, awesome, let me know if you need any help18:49
rsalvetijhodapp: sure, thanks18:49
alexabreuom26er, but the debug one is fine (the debug policy is afaik automatically added by qtc, but has to be removed when uploading to the store)18:50
om26eralexabreu, thats not in the list: http://i.imgur.com/9YjxI2p.png18:54
om26ershould I install 15.04 on my desktop18:55
alexabreuom26er, try the 14.10-dev2, or install 15.0418:55
om26erHahaha, says : 14.10-dev2 is obsolete.18:56
charlesrobru, the branches in line 62 are fixed now19:30
robrucharles: ok, silo is good to go19:32
charlesrobru, thanks19:32
robrucharles: you're welcome19:32
om26erbzoltan_, where can I see the ui-toolkit test plan results ?19:56
dobeyfginther: hey. so, my branch that adds the autopkgtest bits and makes the autopilot tests run is in trunk now. the tests still won't run under mir yet, but i wonder if we should enable them so they get run on MPs, and just not fail MPs for failed AP tests yet?20:25
zbenjaminpopey: the could not find a shell thing wasn't it because you used terminator?20:33
robrucharles: rtm silo 420:45
charlesrobru, ack20:46
rsalvetibfiller: kenvandine: jhodapp: image 98 is out: http://people.canonical.com/~ogra/touch-image-stats/98.changes20:55
kenvandinersalveti, thanks!20:56
kenvandinenow i can worry less :)20:56
bfillerrsalveti: thanks20:56
jhodapprsalveti, nice, thanks man20:57
bfillerrsalveti: will need to do the same thing next week on rtm, actually just the seed will need to be updated once my silo is synced20:57
rsalvetibfiller: sure, no worries20:57
rsalvetijust let me know when you need it to be updated20:57
bfillerrobru: fyi, seems to be an off by one error in the dashboard with the spreadsheet row21:18
bfillerrobru: reports one row higher than where it really is21:18
bfillerdamn 0's and 1's :)21:19
robrubfiller: looks right to me, but I did notice something like that earlier today. try reloading the spreadsheet.21:19
bfillerok21:19
bfillerrobru: yup it's fine now21:20
robrubfiller: hehe. amazingly the dashboard knows the spreadsheet row better than the spreadsheet does ;-)21:21
=== salem_ is now known as _salem
fgintherdobey, that can be done, we'll let you know when it's ready21:34
dobeyfginther: great thanks. i'm going to be heading out soon since it's about EOD here. but just ping me and i'll see it later.21:38
charleshurm?22:08
* charles looks22:08
charlesah, it didn't get top approved, and dobey's already EODed.22:11
charlesI'll be a little tacky and top-approve myself22:11
rsalvetibfiller: can't we make https://bugs.launchpad.net/barajas/+bug/1421091 part of silo rtm 11?22:21
ubot5Error: launchpad bug 1421091 not found22:21
rsalvetibfiller: it's also a critical factory issue22:21
robrukenvandine: around for a packaging ack? https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-019-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-themes_14.04+15.04.20150213~rtm-0ubuntu1.diff/*view*/ thanks22:43
robrukenvandine: https://ci-train.ubuntu.com/job/ubuntu-landing-021-2-publish/lastSuccessfulBuild/artifact/packaging_changes_compiz_1%3A0.9.12.1+15.04.20150213-0ubuntu1.diff/*view*/ another one if you can22:58
robruMirv: congrats: 11G./silos/ubuntu/landing-005 13G./silos23:33
robruawesome.23:44

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!