[02:05] === IMAGE 103 building (started: 20150218-02:05) === [03:05] === IMAGE RTM 239 building (started: 20150218-03:05) === [03:30] === IMAGE 103 DONE (finished: 20150218-03:30) === [03:30] === changelog: http://people.canonical.com/~ogra/touch-image-stats/103.changes === [03:40] trainguards, Can I get a silo for line 51? [03:41] tedg: ha! you just caught me on the way out for dinner. silo 11. [03:43] robru, Awesome, thanks! :-) [03:45] tedg: you're welcome [04:20] === IMAGE RTM 239 DONE (finished: 20150218-04:20) === [04:20] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/239.changes === [04:23] Hmm, that answers that question. [05:41] morning [05:47] hmm, wtf happened to my qtdeclarative line on spreadsheet, and how does it seem bzoltan's line 40 has kind of assimilated it [05:49] bzoltan_: could you look at line 40 and and least make it like you'd like it to be? the MP is about phablet-tools, yet the bug is about qtdeclarative and it has qtdeclarative as manually uploaded package [05:49] Mirv: geez... not again a CI sheet conflict [05:51] bzoltan_: I haven't seen that, but is it something like not everything is shown to everyone, then they add a line, and they somehow get mixed up? [05:51] I can see sil2100 "reconfigured" my silo adding phablet-tools to it.. https://ci-train.ubuntu.com/job/prepare-silo/4142/console [05:51] but the bug link isn't from my line even [05:51] yes it's qtdeclarative but not the bug my landing in silo 012 was supposed to be about :S [05:52] Mirv: I do not know. I deleted the crap [05:52] Mirv: I have not added those junk text there :) [05:53] bzoltan_: this make me very trusting that the rest of the spreadsheet has not gone completely mixed :) [05:54] bzoltan_: ok, you've your silo now reconfigured to have your actual landing, and I readded my own line [05:55] Mirv: bzoltan_ I've been seeing a lot of mixups like this lately, whenever it happens to you, please reload the sheet. Sometimes it goes away. [05:56] robru: it can't go away if a silo has already been reconfigured to have two landings mixed :) [05:56] Mirv: true [05:56] go Google! [05:57] Mirv: yeah i dunno how this is getting worse, replacing the spreadsheet is top priority [06:52] ogra_, hey, if/when you’re around, I need a packaging ack for https://ci-train.ubuntu.com/job/ubuntu-landing-025-2-publish/17/artifact/packaging_changes_webbrowser-app_0.23+15.04.20150217.1-0ubuntu1.diff [06:54] trainguards: good morning! I need a binary copy of oxide-qt 1.5.3-0ubuntu1 from https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+packages to silo 3 [06:55] Mirv: can you grab that? I'm afk [06:58] robru: sure [06:58] oSoMoN: sure [06:58] * Mirv is very sure [06:58] Mirv: thanks ;-) [06:58] oSoMoN: I tried also on #ubuntu-devel but maybe we need ogra if no-one else volunteers [07:01] oSoMoN: we got it from mitya57 === oSoMoN_ is now known as oSoMoN [07:04] Mirv, thanks! [07:04] now all I'd need is an archive admin to approve compiz-mate binary package addition, no luck yesterday or today so far [07:17] Mirv: was the rtm image 237 ditched or what? [07:29] Mirv: Hmmmmmmm silo 3 diff is empty, that's suspect. [07:31] bzoltan_: I'm not sure, you mean in terms of verification? I think signoffing and landing is still ongoing today. [07:31] robru: maybe because it needs to diff around 2.5GB against another 2.5GB, something runs out? [07:32] robru: luckily not disk space though :) [07:33] Mirv: I should hope that debdiff tool doesn't explode just because the filesize [07:33] robru: no, it's not that, I've debdiffed oxide locally just fine [07:33] Mirv: I'm poking at it now... [07:35] Mirv: oh I see... one sec [07:38] * ToyKeeper wonders when bfiller gets up... probably not for several more hours [07:39] ToyKeeper: gets up? hah! he probably just went to bed recently. it's not even midnight us west coast [07:39] Probably need to confirm if a silo can land even though the bugfix has an unfortunate side effect. [07:39] (in rtm-017, one of the bug fixes eliminates an accidental feature which allowed it to produce higher-quality photos) [07:41] Mirv: oh btw, what I told you before about needing FORCE_REBUILD and WATCH_ONLY to regenerate diffs is no longer true. WATCH_ONLY now regenerates diffs by itself, that seemed more sensible to me. [07:44] robru: right, that's great! [07:44] ToyKeeper: the usual default is indeed that flash is used for focusing if when flash itself is turned off [07:45] Mirv: But it no longer uses the flash for focusing after applying this bugfix. [07:46] ToyKeeper: yes, I just mean that indeed that's wrong, the default should be flash used for focusing even if there wouldn't be a setting for controlling it [07:47] or well, I have seen also phones that do this same thing. [07:47] Ah, okay. So it sounds like this is less a grey matter and more of a fail. [07:47] yes it's a rather grey matter. some people prefer that they can actually make the phone not to use the flash (for example it's banned to use flash in museums) [07:48] Oh, it definitely is better to have the option rather than letting the phone be too smart for its own good. :) [07:49] But I feel that way about pretty much any attempt at software being clever. [07:56] Mirv: I mean that the RTM #237 is not listed here -> http://people.canonical.com/~ogra/touch-image-stats/rtm/ But it was the latest proposed when I validated the UITK landing... and it brought a broken gallery what made my testing invalid. Not nice ... [08:01] Mirv: hah: https://ci-train.ubuntu.com/job/ubuntu-landing-003-1-build/lastSuccessfulBuild/artifact/full_oxide-qt.diff/*view*/ 366MB diff, got it working at least. [08:08] robru: now we just need to review it properly! [08:08] but yes, working = good [08:08] Mirv: good luck ;-) [08:09] bzoltan_: that's probably just ogra's scripts not running or something, as it's missing 237+238 [08:09] well, there were most likely device tarball or custom tarball changes ... if there are no rootfs changes -> no changelog [08:10] oh right, there were those [08:10] is anyone looking at u1 accounts being lost on rtm > 234 updates? [08:10] seb128, it is most likely due to the server wanting to refresh the token ... [08:11] your token gets invalid on the phone when that happens [08:11] we need better user feedback for this [08:11] why is that happening only after an update? [08:12] ogra_, dbarth is saying something else on -touch [08:12] dunno ... before the old account stayed around and people were wondering why app updates stopped workin [08:12] seb128: apparently because the apparmor extension is missing, and the u1 lib now expects it to be there [08:12] how could that lib land without this in place ? [08:13] this needs to be a dependency then [08:14] https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1392380/comments/17 [08:14] Launchpad bug 1392380 in signon (Ubuntu RTM) "OA gives out all tokens to any app" [Undecided,In progress] [08:14] so yeah [08:14] bug, not token from server issue [08:15] ogra_: Mirv: anyhow, there must be a gallery app change between 236-237 what introduced failing tests [08:16] seb128, well, 239 has the fix then [08:17] my u1 account is not back though [08:18] dbarth, ^ do we need to add the account again anyway? [08:20] ogra_: Mirv: can you guys confirm this gallery change? [08:21] bzoltan_, i can confirm that no rootfs changes happened :) [08:21] nothing else [08:21] bzoltan_: ogra_: no, gallery is 2.9.1.1136 from end of January [08:22] ogra_: so you say that the 236 and 237 are identical? Because I did capture a gallery test regressions. [08:22] no, i say that the rootfs hasnt changed [08:22] iirc 237 had some fixed for factory mode or so ... [08:23] *fixes [08:23] in the device tarball [08:23] and 238 was a new custom tarball ... no idea what changed there [08:24] Mirv: Ok, the gallery did not change. What about the gallery tests? [08:24] bzoltan_: the RTM branch of gallery is untouched [08:25] bzoltan_: but, maybe the phablet-click-test-setup checks out trunk instead? [08:25] Mirv: something caused the gallery test failures from 236 to 237 [08:25] bzoltan_: oSoMoN fixed gallery-app test failures in _trunk_ 19 hours ago https://code.launchpad.net/~phablet-team/gallery-app/trunk [08:25] if phablet-click-test-setup checks out trunk AP:s instead of rtm AP:s, that would explain it [08:26] Mirv: Yeps... that was it. 19 hours ... that is exactly between my reference and silo testing [08:26] bzoltan_: so it's not tests failing, it's wrong tests [08:27] bzoltan_: but nothing in rootfs really changed in 237 and 238 [08:27] Mirv: Clear. === 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: ubuntu-rtm landing gates now closed [08:41] brendand: jibel: Guys, I have marked the silo1 tested and pasted the test results to the usual cell in the sheet. The silo validation for UITK takes ages, like 12-14 hours a round. You do not need to run the test plan. All the tests are done. If you have questions please ping me _and_ kalikiana. I hope that this UITK fix can make it to the the w9 freeze. [08:43] bzoltan_: we'll have a hangout in 45mins, after that we'll know more [08:44] Mirv: Cool :) please push the UITK :) [08:45] bzoltan_, that'll be short for this milestone. There are still huge updates in the queue, like calendar and camera [08:45] bzoltan_, but we'll do our best [08:49] jibel: it is up to you guys. The cursors issue this UITK fixes seemed to be rather important [08:49] dbarth, so, should I add back my u1 account manually, or keep it in that state in case somebody wants to fix it and need a system to verify the fix on? [08:56] Mirv, any idea why QLibrary.load() would fail? [08:58] Mirv, the error looks like this - http://pastebin.ubuntu.com/10287481/ [09:00] brendand: at least out of context that doesn't tell me anything.. it'd sound like it doesn't find a library or something? [09:01] Mirv, yeah. i'm not really sure where it looks [09:02] Mirv, the location is on both QT_PLUGIN_PATH and LD_LIBRARY_PATH [09:15] seb128: you can add it back, we have a way to reproduce in a bug report [09:15] dbarth, thanks [09:15] seb128: mardy is looking into this right now [09:15] great [09:52] sil2100: jibel if we add calendar to dashboard, won't that need calendar to already be in the image? [09:52] seb128: hey! Do you know if there's any progress made on the failing ubuntu-system-settings AP tests? [09:52] popey: it will be in the next image unless things go very wrong [09:53] popey, it should be on next image [09:53] ok [09:53] popey: as they mentioned, it should be in the next image so we should be safe to add it now [09:53] ok [09:53] and if it is not and it fails, we'll know why :) [09:53] hah [09:53] sil2100, no, we have no clue what's the issue, we can't reproduce on devices and the issue on the ci run seems in qtfeedback [09:53] seb128: the changes that are causing almost all tests to fail also landed on ubuntu-rtm yesterday and we would need those fixed before we can get an image promoted [09:53] that's what I understood from what Ken said the other day [09:53] oh [09:54] cihelp Hello! Can we please get calendar app autopilot tests added to the dashboards? (it was removed a while ago, but we're adding it back to the image) [10:08] sil2100: jibel: I saw that we have time until 2pm UTC. Who to bribe to pull the UITK up in prioroty? It has a fix what effect _ALL_ text input in _ALL_ apps. [10:08] bzoltan_: no worries, QA will sign-off your silo after silo 11 and calendar [10:09] sil2100: Okey...now all I need is an IBAN number and a sum :D === iahmad__ is now known as iahmad [10:32] sil2100, +1 for gallery app [10:33] \o/ [10:33] Publishing [10:35] sil2100, you upload to the store as well? [10:35] jibel: and what about the qtdeclarative5-ubuntu-ui-extras0.2 package in the end? [10:35] sil2100, it is wrong in vivid too. You have a click app that depends on an external lib that is not part of the framework but added manually to the seed [10:36] jibel: hm, but I don't see it in ubuntu-rtm right now - will we need to land the camera-app silo first? [10:36] rmadison says it's only in vivid currently [10:37] sil2100, it's in 17, bfiller said "No because gallery-app click package does not need ui-extras0.2 yet and we are not installing the gallery-app deb which has this dependency" [10:38] sil2100, I don't quite understand why the click package wouldn't need this lib [10:39] sil2100, the lib is not embedded in the click package, so if it is not installed on the system it'll use the wrong version [10:39] Ah, hm [10:39] Ok [10:39] sil2100, I don't know what in gallery app uses this lib and if it detects which version is available at runtime [10:40] sil2100, I think it's safer to wait for silo 17 to land too [10:40] Not sure what to do in this case, as even though the .deb packages are basically just dummy ones, but this will mean I'll push a broken-dep package to the archive [10:40] jibel: yeah [10:40] Ok, let's just wait then :) [10:40] Thanks! [10:41] sil2100, but IMO this lib should be a dependency of an ubuntu-sdk-lib-extras which would be a suggest of ubuntu-sdk-lib and -extras would be added to the seed. and if the version of the lib changes you bump the version of the framework [10:43] sil2100, probably cleaner than adding that lib manually to the seed. You cannot even track which click package depends on it, and that'll probably break stuff next time it's updated to a major version === vrruiz_ is now known as rvr [10:54] popey: I've added your request to our 'To do' lane [10:54] Doing this should not take that long but it could be a little while for us to get there [10:54] s/there/to it [10:54] thanks psivaa_ [10:54] np === dpm_ is now known as dpm === marcusto_ is now known as marcustomlinson === _salem is now known as salem_ [11:28] cihelp: on http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/239:20150218:20150216-fe747ac/332/ 3 tests are failing because system-settle failed (abook, dialer and calc) Where do I find info why it failed? There is not much info in top-before and top-after log files [11:29] jibel: ogra_ had a nice script to parse it for useful information [11:30] ogra_, ^ do you mind sharing your script? [11:30] paste.ubuntu.com/10289122/ [11:31] i havent used it in ages, not sure it still works [11:31] ogra_, I'll try, thanks! [11:32] jibel: pas mieux [11:34] sil2100, ogra_ I don't see anything interesting in topafter but it's likely the scoperunner crash that generated the load [11:35] davmor2, did you notice any crash while testing the custom tarball? [11:36] jibel: nope [11:42] I go prepare lunch [11:45] popey: Calendar app: text: "W"+ root.startDay.weekNumber() [11:45] popey: "W" must be localized [11:46] popey: Also, pot file needs update, "All Day" is not available in Launchpad for translations. === MacSlow is now known as MacSlow|lunch [12:24] sil2100: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-005-1-build/112/console ... [12:24] sil2100: I once ran build with watch_only quite quickly after uploading the final version, now it's like that.. [12:25] huh? [12:25] sil2100: I guess just another way CI Train may "save" some wrong information and not clear that out [12:25] sil2100: note how it checks two versions of the same package [12:26] Mirv: yeah, probably try doing a normal non-watch_only build [12:26] But I guess it's a bug indeed [12:26] watch_only should not use any saved state for source packages [12:26] sil2100: normal build same problem it seems https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-005-1-build/113/console [12:27] huh [12:27] Ok, now that's broken then [12:27] Let me take a look in-between frying === alan_g is now known as alan_g|lunch [12:33] hm [12:34] Mirv: from the CI Train side everything looks ok, I wonder what the new build job does [12:35] sil2100: the old version is not even shown at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-005/+delete-packages anymore [12:37] rvr: can you file a bug pls? [12:38] sil2100: maybe it's still something that will sort itself by time, ie. the LP query will return different results at some point. [12:38] popey: Yes, we can [12:39] thanks [12:43] popey: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1423160 [12:43] Launchpad bug 1423160 in Ubuntu Calendar App ""All day" and "W" (for week) not translatable" [Undecided,New] [12:43] thanks rvr [12:57] sil2100: ok, it still failed I now did _both_ prepare-silo reconfig + tagged force_rebuild of both packages (even though they are manual uploads and not MP:s). either of them finally cleared the wrong info out. [13:00] Mirv: geh, ok... === alan_g|lunch is now known as alan_g [13:18] trainguards: question: the silo request on row 56 does not change existing code, just remove some toos that were not being used for quite some time on history-service, do I need to put QA signoff as Required still? [13:28] boiko: I would say it shouldn't require sign-off, since the diff indeed looks sane [13:28] boiko: but shouldn't you also remove history-service-tools from debian/control? [13:28] sil2100: well, that's the thing: on vivid we added new tools, I just don't want to backport them right now [13:40] boiko: ok, yeah, but in ubuntu-rtm it would mean that we'll have an empty package basically, right? [13:40] Not a super bad thing though [13:41] sil2100: yep, at least until we backport the new tools (they help testing, as they populate the history database, etc) [13:54] trainguards: hi, could I get vivid silo 011 reconfigured please? thanks! [13:56] pete-woods: sure [13:56] pete-woods: done [13:56] Mirv: ^ [13:57] sil2100: hehe :) [13:57] pete-woods: and thanks for the fix already in advance! [13:57] boiko: ok, assigned the silo, but QA might want to re-discuss the requirement of sign-off [13:58] sil2100: that's fine, I was just trying to leverage their work :) [14:00] jibel, sil2100: gallery-app click package does not depend on ui-extras0.2 yet so that is not needed technically [14:00] it will need it in the future but doesn't right now [14:00] Mirv: well, importantly this won't be truly fixed until the apps are updated to stop doing their own translations for infographics (see MR for music-app https://code.launchpad.net/~unity-team/music-app/infographics-translations/+merge/248251) [14:02] sil2100: kenvandine can ack the packaging changes in silo 18, he's aware of the situation [14:02] hey bfiller [14:02] bfiller: ok... if a core-dev acks that then it's fine, but basically right now the deb will be uninstallable on ubuntu-rtm [14:02] I know we don't use the .deb basically [14:02] sil2100, have you seen anything like this? http://pastebin.ubuntu.com/10290989/ [14:03] But if something lands in the archive it should have archive-sufficient quality === MacSlow|lunch is now known as MacSlow [14:03] sil2100: yes that is true, but we don't use the deb at all. it's only there for convergence to install on desktop [14:03] bfiller: I'll let kenvandine as the core-dev to decide ;) [14:03] sil2100: so lets sync ui-extras then from vivid at the same time [14:03] bfiller: yeah, it's in another silo which seems to have some problems currently [14:04] Otherwise I would just sign-off and land both [14:04] sil2100: we can move that into it's own silo so it can land independently [14:04] bfiller: no worries, let's wait a bit on how things resolve and decide then if we need to hack around it [14:04] sil2100, i'm fine acking that for rtm [14:05] we aren't running desktops from rtm anyway [14:05] sil2100, kenvandine : ok thanks guys [14:05] Ok then, let me publish it :) [14:05] thanks [14:05] sil2100, and look at that pastebin when you get a chance :) [14:05] kenvandine: ok, looking now [14:05] bfiller, there is a fix for the camera, so it should land later today, and ui-extras0.2 too [14:05] that's what we're getting from smoke tests [14:06] sil2100, which i've reproduced on my krillin running vivid locally [14:06] kenvandine: hm, now that's something I never saw before [14:06] also... [14:06] kenvandine: it started happening after the u-s-s silo landed... was there anything risky in it? [14:06] this started happening between image 96 and 98 [14:06] which had a massive mir landing [14:06] jibel: ok cool, thanks [14:07] sil2100, there was also a mir landing [14:07] there was nothing risky in the silo [14:07] sil2100, in fact... the only change in that silo was adding some UI that is hidden [14:07] kenvandine: but not in ubuntu-rtm - and we see the same failures in rtm with the latest image [14:07] wait... same thing in rtm? [14:08] kenvandine: http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/239:20150218:20150216-fe747ac/332/ <- this is the latest result in rtm after landing of the u-s-s silo, no failures seen before this [14:08] http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/239.commitlog [14:08] These are the changes [14:08] sil2100, so the same change landed in rtm, and the UI isn't hidden there [14:09] This is why I started thinking that it's this landing that's responsible [14:09] sil2100, what image did it start happening in for rtm? [14:09] WIth this one [14:09] 239 [14:09] that is the latest right? [14:09] http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/ <- all others have normal failure counts [14:09] Yes :) [14:09] well wtf@ [14:09] We would really like to have this resolved as it's blocking our promotion [14:10] sil2100, the change we landed in 239 also landed yesterday in vivid [14:10] Since releasing OTA-1 with so many failures is really bad ;p [14:10] this has been happening for over a week in vivid [14:10] hmm [14:10] Interesting [14:10] sil2100: I will push the gallery-app click to the store now, is that ok? [14:11] sil2100, and... the only change in the image that this was introduced in with vivid had landed in rtm a week before it landed in vivid [14:12] kenvandine, hey, getting anywhere with the u-s-s test issue? [14:12] #15 0xaf0763ce in QFeedbackHapticsEffect::QFeedbackHapticsEffect(QObject*) () from /usr/lib/arm-linux-gnueabihf/libQt5Feedback.so.5 [14:12] same damn thing [14:13] seb128, that's what sil2100 and i are talking about [14:13] seb128, it just started happening in rtm smoke testing [14:13] kenvandine, weird [14:13] in image 239 [14:13] brb [14:13] seb128, and there are strange logs [14:14] http://pastebin.ubuntu.com/10290989/ [14:14] seb128, ^^ thoughts? [14:14] kenvandine, not really, does it have to do with screencasting? [14:15] how is the screencasting working? [14:15] oh i wonder if that is what's causing that log [14:15] i don't know [14:15] can we enable it locally to see if we hit the same issue? [14:16] i have reproduced it locally [14:16] on my krillin with vivid [14:16] oh [14:16] that can't be screencasting [14:16] i get that same log output locally [14:16] k [14:16] [1424235205.472568] mircommon: Caught exception at Mir/EGL driver boundary (in setSwapInterval): /build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): Throw in function virtual void mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int) [14:16] Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_errorEEEE [14:17] that part anyway [14:17] did mir change in rtm?! [14:17] seb128, and at the same time, there's a seg fault from uss that seems to be triggered by haptic feedback [14:17] seb128, i don't think so [14:17] not in image 239 [14:17] weird [14:18] seb128, but... there was a mir landing in the first vivid image that had this problem [14:18] doesn't explain why rtm get the same issue without a mir landing [14:18] qtdeclarative5-ubuntu-ui-toolkit-plugin changed in image 236 [14:20] seb128, the good news is this crash really happens at the very beginning of the test [14:20] everytime [14:20] and we aren't seeing this crash manually testing [14:21] so it must be something to do with the autopilot tests [14:21] and i've ruled out infrastructure by testing locally [14:22] i wonder if we're the only ones seeing this because we don't use upstart-app-launch [14:35] seb128, https://errors.ubuntu.com/problem/b4ceece27f0ccfe9753e940695015237461b3908 [14:35] kenvandine, not very useful, why isn't retracing working? [14:36] popey: can your review/ack new gallery I just uploaded to store? [14:36] seb128, that's what i was going to ask you :) [14:36] bdmurray, ^ can you help there? [14:37] bfiller: done [14:38] also... all 3 instances of it where run by autopilot [14:39] seb128, https://errors.ubuntu.com/problem/f1aceaefc06bcc522f22df201625eb2d111929fb [14:39] that one has a retrace [14:40] Publishing o/ [14:40] kenvandine, right, who is working on the feedback plugin? [14:40] that's from qt [14:41] bfiller: anyway, can you please upload the new gallery-app to the store? :) [14:41] seb128, i'd think that would affect all kinds of stuff [14:41] we don't do anything directly there [14:41] just the uitk [14:42] seb128, i created bug 1423205 [14:42] bug 1423205 in ubuntu-system-settings (Ubuntu) "/usr/bin/system-settings:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::Bus" [Undecided,New] https://launchpad.net/bugs/1423205 [14:43] sil2100: done, popey just approved it [14:43] Excellent [14:44] sil2100: can I get a silo for line 58 on vivid, it's the camera-app fix need to land it in vivid first then will sync to rtm [14:44] Sure, on it [14:44] jibel: ^^^ the camera-app is fixed, just doing the vivid landing first then will update the rm silo [14:44] rtm silo [14:46] kenvandine, Hi! [14:47] kenvandine, I am trying out silo 14. If the device does not discover the bluetooth name of the headset, it shows its MAC address, is it supposed to keep showing that until I connect to the headset ? [14:48] as long as it doesn't detect a name [14:48] it should [14:48] bfiller, OK, rhuddie ^ can you reverify the camera after silo 3? [14:48] kenvandine, how long does it take to detect the name generally ? [14:48] om26er, it might never [14:48] rhuddie, when it's in the silo of course :) [14:48] that was part of the problem [14:48] it would display an empty name [14:48] s/part// [14:49] jibel, sure. i just finished silo 3. [14:49] kenvandine, I think we need to add a testcase to the testplan for this bug fix. [14:49] om26er, so you have a device that doesn't get a name? [14:49] rhuddie: I'll ping you soon when it's in the rtm silo [14:49] kenvandine, it showed its MAC address [14:49] bfiller, thanks. [14:49] om26er, to properly test this specific case, the tester needs a device that wouldn't show a name [14:50] hmmm, don't have that. [14:50] om26er, i don't have a device that doesn't show a name [14:51] kenvandine, let me clear there are three cases ? 1. where name is shown. 2. only MAC address, 3. No nothing and in that case we want to show "..." ? [14:51] om26er, for case 3 we want to show the address [14:52] om26er, it should only show the address when there is no name detected [14:52] om26er, i don't have any devices that don't show a name [14:52] for example [14:53] om26er, so showing the address shouldn't be common, i'd hope [14:53] I tried it in my car it showed the MAC address, the name only appeared when I connected to it. [14:53] om26er, cool, i think that's what we want [14:53] om26er, but there are some devices that'll never get a name [14:54] so we'll keep showing the address [14:54] om26er, but to test that you need a device that doesn't get the name [14:54] not sure we want to require everyone that tests this to have such a device [14:55] heh, I'll just approve it after some more testing. [14:56] om26er, thx... not sure how to test it [14:56] we tested it for regressions [14:56] well, pmcgowan did, not sure if he had a device that didn't detect the name or not [14:57] i tested it in vivid, all my devices still show the name [14:58] kenvandine, om26er my device initially shows the address, then when connnected switches to the name [14:59] pmcgowan, and is that the same behavior as before? [14:59] kenvandine, before the field was blank the the first page, now it shows the address [15:00] pmcgowan, perfect! === plars changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: ubuntu-rtm landing gates now closed [15:00] so you have a device that reproduced the bug :) [15:00] pmcgowan, i tried everything in my house that has bluetooth... they all show a name before connecting [15:01] yeah my headset showed the issue, whereas my car showed the name [15:01] probably a bt version thingy [15:02] sil2100, jibel any chance we will get all the queued silos landed? [15:03] pmcgowan: yes, although we might still be blocked on the failing autopilot tests for ubuntu-system-settings anyway [15:03] pmcgowan: since currently we have almost all u-s-s tests failing [15:03] kenvandine, looking at the diff, previously if device was not paired you appended "..." now you are doing that for the opposite. Intentional ? [15:03] pmcgowan, all the critical fixes will land (9, 14, calendar and camera are under verification) [15:03] kenvandine is looking into that [15:03] pmcgowan: btw. did you hear anything about us not to include calendar-app? [15:04] hmm [15:04] * ogra_ wonders why rmadison gives him 503 errors [15:04] pmcgowan, we'll maybe have time to land silo 1, depending how it goes with silos under testing. [15:05] jibel, silo 0 is also a customer report fix [15:05] and silo 20 just looks like great fixes [15:06] but gotta stop sometime [15:06] pmcgowan: but 0 doesn't seem to look ready [15:06] pmcgowan, but it is not ready for QA. last comment from rsalveti is "Not yet to be validated, WIP (had tested as yes by accident)." [15:06] ok [15:06]