/srv/irclogs.ubuntu.com/2014/03/10/#ubuntu-ci-eng.txt

tvossgood morning07:20
tvossMirv, good morning07:20
Mirvhi tvoss07:22
tvossMirv, looking at the sheet, line 907:23
tvossMirv, I don't understand the comment there07:23
tvossMirv, could you explain to me what happened?07:23
Mirvtvoss: it seems it has been published, but is stuck in -proposed for some reason07:29
Mirvhttp://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#dbus-cpp07:29
Mirvarm64 has failed to build, but it succeeded before: https://launchpad.net/ubuntu/+source/dbus-cpp/2.0.0+14.04.20140307-0ubuntu107:30
Mirvseems to be the reason07:30
Mirvhttps://launchpadlibrarian.net/168638213/buildlog_ubuntu-trusty-arm64.dbus-cpp_2.0.0%2B14.04.20140307-0ubuntu1_FAILEDTOBUILD.txt.gz07:30
tvosshmmm, that's weird07:31
tvosscjwatson, good morning07:38
tvosscjwatson, I get a build failure here https://launchpadlibrarian.net/168638213/buildlog_ubuntu-trusty-arm64.dbus-cpp_2.0.0%2B14.04.20140307-0ubuntu1_FAILEDTOBUILD.txt.gz07:38
didrocksMirv: hey, can you provide an url if you still have the same issue?07:39
didrocksfor the silo stuff07:39
didrocksoh found the issue07:40
* didrocks fixes07:40
didrocksah no07:40
didrockshum07:40
Mirvdidrocks: I haven't yet retried since I thought you'd take a glance first07:41
didrocksMirv: yeah, please give me a link07:41
didrocksyou didn't in your email07:41
Mirvdidrocks: it's in my last e-mail bu http://162.213.34.102/job/prepare-silo/421/console07:42
didrocksMirv: ah, ok, was still on the first one07:42
didrocksthanks07:42
didrocksyeah, weird that we have WARNING:root:Can't load configuration: No JSON object could be decoded07:42
didrocksMirv: I'll look in a few07:42
Mirvyep, that one is weird07:42
Mirvyeah, no hurry. I found 4 more packages not yet in landing PPA, and 3 of them are manual uploads which I'm doing now.07:43
didrocksok, we'll get that fixed07:46
didrocksthe logic seems good, so it's like it can't find the initiale configuraiton07:46
didrocksI'll check with debug :)07:46
didrocks(10 minutes)07:46
didrocksMirv: ah, interesting, the config file is empty07:58
* didrocks restore and try07:59
didrocksMirv: did you have any failure previously on that silo?07:59
didrocksMirv: and after that, all work like expected. It would be interesting to know what lead in your silo to have that empty config file08:00
didrocksMirv: running http://162.213.34.102/job/prepare-silo/423/console btw08:02
Mirvdidrocks: the only thing I did was aborting build job, because of a ppc64el build that the system thought was building while it was not08:07
Mirvdidrocks: I got the error twice in the row and stopped at that. interesting.08:08
didrocksMirv: yeah, shouldn't happen08:08
didrocksMirv: tell me next time you see it, I'll be interested in fixing this bug08:08
didrocksnot sure, I try to always have transactional writes08:08
Mirvsure, I will08:08
didrocksthanks ;)08:08
didrocksMirv: on your question: please for those package, just disable them in daily release08:09
didrocks+ upstream merger and so on08:09
didrocks(the 3 lines)08:09
Mirvdidrocks: ok, thanks, I'll disable those: dee-qt qtpowerd poppler-qml-plugin u1db-qt ubuntu-system-settings-online-accounts unity-scope-online-music click-update-manager clickmanager-plugin ubuntu-purhase-service08:10
Mirvwell, some of them already are, but anyhow08:12
didrocksok ;)08:23
popeybug 128980408:23
ubot5bug 1289804 in Ubuntu Music App "Music app consuming lots of memory on mako 226" [High,Triaged] https://launchpad.net/bugs/128980408:23
popeyseems we have a memory leak issue..08:23
popey(not just music-app)08:23
didrockspopey: blocker in your opinion?08:23
popeybeen there a while08:23
popeybut worse than it was in #194.08:24
didrockspopey: they will tell you they will only look with 5.2 :p08:24
popeywe tested with 5.2 too..08:24
popeyhttps://bugs.launchpad.net/music-app/+bug/1289804/comments/908:24
ubot5Ubuntu bug 1289804 in Ubuntu Music App "Music app consuming lots of memory on mako 226" [High,Triaged]08:24
didrockspopey: argh, ok08:25
popeyso no, not a blocker to #22608:25
popeyit manifests itself in music because it's unconfined, you can get any app to eat ram by keeping it alive with taps08:25
popeyso it certainly needs examination08:25
didrocksyep :)08:26
didrockshum08:26
popeymy phone was unusable after 20 hours of uptime and no usage ☻08:26
didrocksI received the notification for the team meeting08:26
popeyamericans changed TZ08:26
didrocksmeaning the meeting is not set in UTC?08:26
popeyit moved here too08:26
popey(the meeting moved) - it shows at 08:30 UTC08:26
didrockslet me adjust the time again08:26
popeyprobably the Ubuntu Engineering calendar is USA TZ08:27
ogra_didrocks, you will have to adjust back on the 30th08:27
didrocksogra_: yep08:27
didrockspopey: weird, the Tz set for it is "France" though08:27
didrocksanyway, let's move them08:28
didrocksand we'll move them back08:28
didrocksoh, there is one everyday?08:28
didrocksit's a separate one :p08:28
didrocksah no, phew08:28
didrocksjust long to refresh08:28
popeyno, they are separate08:28
popeyi moved some ☻08:29
didrocksahah :)08:29
didrocksthe 6PM as well?08:29
didrocksor they didn't move?08:29
popeyoof, I broke, let me fix08:30
didrocksremoving as well meetings during vUDS08:30
popeyah yes08:31
didrocksvUDS is so empty!08:33
* didrocks scheduled last client meetings in seb128's track08:33
didrockshehe :)08:33
popeydidrocks: who 'owns' ubuntu-emulator? xnox?08:40
didrockspopey: yeah, the biggest contributors are xnox/cjwatson/rsalvetti AFAIK08:40
popeyhm, ok08:40
tvossdidrocks, good morning08:41
sil2100Finally made it08:41
sil2100Morning!08:42
didrockshey tvoss, morning08:42
didrockshey sil2100 :)08:42
didrockspopey: anything we should be worried about?08:42
popeysaw a couple of people in -touch mention that their emulator wasn't starting. I tried this morning and I can't get it to build a working image either08:42
popeyjust get a black screen08:42
tvossdidrocks, sil2100 the dbus-cpp landing seems to be stuck in proposed due to arm64 not building. However, the compilation fails with the compiler complaining about -fstack-protector missing08:42
tvossdidrocks, sil2100 the interesting bit is: I think I don't set that explicitly somehwere08:43
popeytrying again from clean.08:43
didrockstvoss: it's the distribution default08:44
tvossdidrocks, that's interesting that it fails on arm64 then :)08:44
tvossdidrocks, https://launchpadlibrarian.net/168638213/buildlog_ubuntu-trusty-arm64.dbus-cpp_2.0.0%2B14.04.20140307-0ubuntu1_FAILEDTOBUILD.txt.gz08:44
didrockstvoss: https://wiki.ubuntu.com/ToolChain/CompilerFlags08:44
didrockstvoss: I guess it's something to check with doko, I have no clue about arm64 if it's supposed to support stack-protector or not08:45
sil2100tvoss: hmm, well, there was no way to test it beforehand on arm64, as I can't set up a arm64 chrrot even08:45
didrocksand if so, why it's set08:45
sil2100tvoss: strange thing - why didn't it fail for the previous dbus-cpp builds?08:45
didrockstvoss: and yeah, I confirm that you don't seem to do anything with the flags that can set it on that arch08:46
didrocks(and so override potential defaults)08:46
didrocksbut you force 4.708:46
didrocksand I'm unsure 4.7 has the right defaults for that arch, I guess doko only cares about 4.808:46
didrockstvoss: that can be a lead to discuss about it with him I think ^08:46
didrockssil2100: previous version was built with 4.7 or 4.8?08:50
sil2100hm, with 4.708:54
sil2100didrocks: since the whole issue we had with location-service being 100% CPU was caused by the 4.7/4.8 incompatibility08:54
didrockssil2100: ok, weird then08:54
didrocksI think tvoss has enough information to know where to look at anyway :)08:55
cjwatsontvoss: Morning.  arm64 doesn't have stack-protector.  Why are you forcing that, though, given that -fstack-protector is on by default in Ubuntu anyway?08:55
sil2100So we pushed a force rebuild on 4.7 + the symbols hack08:55
cjwatsondidrocks: emulator> not me08:55
sil2100Strange anyways!08:55
tvosscjwatson, I'm *not* forcing it08:55
didrockscjwatson: I don't see it in his build flags though, but he's using gcc 4.7, do you think that disabling stack-protector can be missing on that versioN?08:55
cjwatsondidrocks: It's explicitly on the command line08:55
cjwatsonSo it's not GCC's fault :)08:56
cjwatsonWonder if it's cmake08:56
didrocksyeah, I'm looking into that direction08:56
cjwatsonOr dpkg-buildflags08:56
didrocksnothing special on the configure flags08:56
cjwatsonI'd have thought dpkg-buildflags shouldn't have -fstack-protector on arm64 though08:56
didrockswell, I guess all packages would fail otherwise…08:57
cjwatsonthat command line does look awfully like dpkg-buildflags though08:59
didrocksyeah, followed by --param=ssp-buffer-size=4 and so on, with -g -O2 before…09:00
cjwatsonOh09:01
cjwatsondpkg (1.17.5ubuntu5) trusty; urgency=medium09:01
cjwatson  * Allow -fstack-protector on arm64 now that GCC and glibc support it.09:01
cjwatson -- Adam Conrad <adconrad@ubuntu.com>  Fri, 07 Mar 2014 18:47:57 +080009:01
didrockshere we go09:01
cjwatsonSo gcc-4.8 supports it, but of course dbus-cpp is forcing gcc-4.709:01
didrockstvoss: you have your infos ^09:01
cjwatsontvoss: export DEB_CXXFLAGS_MAINT_STRIP := -fstack-protector09:01
cjwatsonwell, conditional on arm6409:02
cjwatsonso, in debian/rules:09:02
tvosscjwatson, so that's in debian/rules?09:02
cjwatsonifeq (arm64,$(DEB_HOST_ARCH))09:02
cjwatsonexport DEB_CXXFLAGS_MAINT_STRIP := -fstack-protector09:02
cjwatsonendif09:02
cjwatsonshould do it09:02
cjwatsonwith a comment that this is because g++-4.7 doesn't have SSP, and it can go away if/when you move to 4.809:02
cjwatsondidrocks,Mirv: the ppc64el build in question was a build *failure*, not so much "building" although that's how the job described it09:04
didrockscjwatson: something stripped out the status file, so it wasn't refreshed anymore. So don't take into account the status reported in that case09:04
cjwatsondidrocks,Mirv: that was qttools-opensource-src, which we got building later09:05
cjwatsonit was definitely not building at the time09:05
cjwatsonor rather it was definitely failed at the time09:05
didrockscjwatson: I'm maybe out of context for that last ping, but the job was running or you were talking about the jenkins job iself?09:05
didrocksitself*09:05
Mirvcjwatson: I think since it started on Friday, it had not yet been build at all. the first failure of qttools was then on Saturday after copy-package https://launchpad.net/~ci-train-ppa-service/+archive/landing-006/+builds?build_text=qttools&build_state=all09:06
cjwatsonI don't know the distinction09:06
cjwatsonMirv: it was dep-wait on qtdeclarative at the time - I checked09:06
Mirvbut on Friday (until Saturday) CI Train was under impression there was a build of ppc64el that was building09:06
cjwatsonthat's why I sent you a qtdeclarative porting branch09:06
Mirvcjwatson: this is what I aborted originally http://162.213.34.102/job/landing-006-1-build/65/console09:06
cjwatsonI was explicitly working on clearing up that job :)09:06
Mirvcjwatson: aha, ok09:06
cjwatsonfrom my point of view the ci-train job was entirely correct - I mean, regardless of fine distinctions, it'd have got stuck in proposed-migration due to the missing ppc64el build, so it was right to fix it09:07
tvosssil2100, pushed an update to https://code.launchpad.net/~thomas-voss/dbus-cpp/fix-race-and-add-tests09:08
tvosssil2100, can you trigger a rebuild?09:08
didrockstvoss: that should be before the include I guess09:09
didrocks(and you can retrigger yourself normally, with ignore step and only set the component you want to rebuild with only rebuild)09:09
didrocksyou don't need sil2100 for that09:10
sil2100tvoss: you can rebuild yourself :)09:10
cjwatsoninclude> I don't know if it matters, but can't hurt to move it earlier09:10
sil2100tvoss: just find the silo on the spreadsheet, press rebuild, log into jenkins (SSO) and press build09:11
sil2100tvoss: maybe write to only 'rebuild' dbus-cpp09:11
didrockscjwatson: ah ok, I was under the impression it was looking for the definition in the env first and won't look at it again, but I just skimmed over the makefile for that, so you're probably more exact than I am. Thanks :)09:12
sil2100didrocks: how do we handle cases when a silo is already in the 'releasing, stuck in proposed' state?09:12
sil2100tvoss: wait a moment with that if anything09:12
didrockssil2100: just rebuild what's needed to be rebuilt and I think you will need the "ignore step" option09:12
sil2100didrocks: ok09:13
didrocksthen, it will rebuild only that component, and track it09:13
sil2100tvoss: let me help you in that then, I'll do this09:13
didrocks(however, it will recollect all commits since latest version in the release pocket and upload with -v)09:13
tvosssil2100, ack09:13
cjwatsondidrocks: this is one of those things where I'd have to read the GNU Make manual carefully, and it's not worth it :)09:13
didrocksbut that was only tested in labs, it's the first time in production :)09:13
didrockscjwatson: heh, indeed :)09:13
sil2100didrocks: uuuu ;p Ok, let's try that then09:14
sil2100didrocks: hmmm... I just noticed my mail, I probably missed something, but was todays landing meeting moved to an earlier hour?09:15
didrockssil2100: it was, weirdly (probably due to US dailylight saving switch)09:16
didrockssil2100: so I rescheduled at the correct time09:16
sil2100My google calendar said 9:30 till 10, like one hour earlier than normally :o Did I miss it?09:16
sil2100Ah09:16
sil2100Ok ;)09:16
didrockssil2100: your google calender should have it updated?09:16
sil2100didrocks: ah, right, calendar has the correct date, but I didn't get a confirmation of the change on e-mail, so I was a bit shocked09:17
sil2100THanks ;)09:17
didrocksyeah, I avoided to spam all of you09:18
sil2100tvoss: let's wait for it to re-build09:26
tvosssil2100, ack09:26
didrockspopey: coming?09:31
popeyomw09:32
cjwatsonMirv: given that we'll be waiting for arm64 to build everything, I would suggest blocking the set of packages in the Qt5.2 silo in proposed-migration10:01
cjwatson(once you push the button)10:01
cjwatsonjust to avoid accidents with partial promotions10:01
popeydidrocks: who should I poke https://bugs.launchpad.net/music-app/+bug/1289804 with?10:03
ubot5Ubuntu bug 1289804 in Ubuntu Music App "Music app consuming lots of memory on mako 226" [High,Triaged]10:03
didrockspopey: reboot worked for you?10:03
popeyyes didrocks10:03
didrockspopey: ok, I don't have it either here in a fresh flashed image10:04
didrocksworth keeping it in mind and see10:04
popeywill keep an eye out for it on future updates10:04
didrocksthanks10:04
didrockspopey: for bug #1289804, I would say let's start with upstream, so osomon/bfiller10:04
Mirvcjwatson: ok, didrocks can probably set the block, at least if it turns out we enable the arm64 builds but then suddenly make a decision tomorrow or so about actually landing it10:04
ubot5bug 1289804 in Ubuntu Music App "Music app consuming lots of memory on mako 226" [High,Triaged] https://launchpad.net/bugs/128980410:04
Mirvarm64 is going to be interesting, starting with qtbase where doko told the arm64 patches can be dropped with 5.2, I hope it's so10:05
didrocksdavmor2: oh btw, can you dogfood image #229? We'll get it in our bag for promotion :)10:06
didrocksMirv: yeah, better to prepare it10:06
didrocksMirv: when is that meeting? Maybe I should come this time10:06
davmor2didrocks: yeah no worries10:07
Mirvdidrocks: umm, I now see the meeting is no more this week, at least currently. it used to be 14:00 UTC10:07
didrocksMirv: interesting…10:07
didrocksMirv: wasn't moved to one hour later? (as many meeting due to US TZ change)10:07
didrocksmeetings*10:07
Mirvdidrocks: no, just not there. probably set to be daily "until we've probably shipped it" or so :)10:08
didrocksMirv: yeah ;)10:08
Mirvthe unity8 AP problem might have a fix now, since I rebuilt qtbase with a fix suggested from unity people10:08
didrocksMirv: tell me if you need anything, but I clearly think that we should continue on what was discussed Friday: only the expected AP failure10:09
didrocksok10:09
Mirvweather app I think was already seen to be broken, probably needs fixes for 5.210:09
didrocksexpected == clock apps as from today10:09
Mirvit'd be nice if gallery app could be tested somehow10:09
didrocksand 2 weather apps ones10:09
didrocksah no, it's one on weather-app10:09
didrocksMirv: so, we expect only 1 clock AP test failure + 1 weather AP test failure10:10
didrocksall the rest needs to be investigated10:10
Mirvdidrocks: I checked that online-acounts does have the revert in it10:10
didrocksMirv: the run from Friday?10:10
didrocksAP test run?10:10
didrocks(the code where we see it failing shouldn't be in the revert at all)10:11
Mirvdidrocks: hmm, actualy, it's a good question whether the AP run or the Friday's online-accounts rebuild was there first..10:11
Mirvdidrocks: so that's probably then it10:11
didrocksMirv: ok, worth having a look anyway :)10:11
Mirvdidrocks: I originally btw thought that if 5.0 image can be promoted, it's good to land 5.2, but you think we continue at least for now seeking to do 100% smooth transition (where, nearer to it than current situation)?10:12
MirvI wonder if UI Freeze on Thursday poses a problem10:12
didrocksMirv: yeah, otherwise, we'll never recover and block everyone else not part of the transaction10:12
didrocksMirv: why? we have FFe for our components (and it doesn't change the UI)10:13
Mirvtrue enough, nothing should change UI wise10:13
didrocksMirv: we can't ask blocking the whole distro again on pushing something not ready when we know it's not ready yet10:13
didrocksthat won't make it more "ready"10:13
MirvI don't think anyone is currently working on the 5.2 related AP problems, though, yet10:15
Mirvthat should change, of course10:15
didrocksMirv: that should have been the focus as well of the 5.2 meetings though10:15
didrocksyeah10:16
Mirvdidrocks: the problem was that for most of the last week the AP runs were not working because of the adb/makodevice problems10:16
Mirvnow we've that one run finally10:16
didrocksMirv: which issue?10:16
didrocksMirv: something we don't have on ci.ubuntu.com?10:17
Mirvdidrocks: I mean the AP runs were not possible to do because of http://q-jenkins:8080/job/autopilot-release-gatekeeper/61/console10:17
Mirvfirst the adb problems and then the connection to mako:s not working, elopio & his team were then onto it10:17
didrocksMirv: ok, so infra issues mostly?10:18
Mirvdidrocks: yes10:18
didrocksMirv: anyway, we discussed about the AP tests on Friday with elopio and asac as well agreed with me10:18
didrocksMirv: so I don't think that will come to a surprise10:18
Mirvyeah. so trying to fix those should continue together with the DPR issue fix.10:19
didrocksyep10:21
tvosssil2100, didrocks I'm kinda lost with the dbus-cpp landing now10:24
sil2100tvoss: ok, wait, it finished building10:25
cjwatsondidrocks,Mirv: landing-006 has arm64 now, so can you please copy everything in that PPA into itself?10:25
sil2100tvoss: let's do a quick test-spin on a device if all is ok and then re-publish10:25
cjwatson(let me know if you need a canned command line)10:26
didrocksMirv: you are handling the copy?10:26
tvosssil2100, okay, I will give it a spin, too10:26
tvosssil2100, could you try it, too?10:26
cjwatsoncopy-package -p ci-train-ppa-service --ppa-name landing-006 -b <list of all the source packages>10:26
sil2100tvoss: sure, doing that now10:26
tvosssil2100, thanks10:27
Mirvcihelp infrastructure problems running AP tests http://q-jenkins:8080/job/autopilot-release-gatekeeper/64/ - previous successful run on Friday10:27
Mirvdidrocks: ok, handling the copy10:28
didrocksthanks :)10:28
Mirvactually, I'll not copy everything, since not everything build-deps on the new Qt. so starting with Qt itself which is all set up good regarding dependencies10:32
cjwatsonwhy the backup-landing1?10:33
cjwatsonoh ye of little faith10:33
Mirvcjwatson: too much to lose :)10:35
cjwatsonyou couldn't copy it back without generating at least some new builds anyway ... but ok10:35
ogra_hmm, promoting takes loong with so many arches10:37
=== pete-woods is now known as pete-woods-afk
Mirvactually, I will start by qtbase only because that's the one with the libqt5core5 -> libqt5core5a change10:38
cjwatsonreasonable, yeah10:38
sil2100wow10:38
Mirvand so it begins10:39
sil2100hmmm, what a nice bug I got!10:41
didrockssil2100: on the double promotion for fixing something stuck into proposed? It's possible as I only tested that case in lab :)10:43
sil2100didrocks: no no, on 229 ;) I'll show a photo of that, it's just a funny thing, I guess it's just some layouting issue or something ;p10:44
didrocksah :)10:45
ogra_grmpf ...10:46
ogra_promotion of 226 on mako runs since 13min ... doesnt move ...10:46
didrocksogra_: still stuck?10:52
ogra_yes10:52
ogra_29071 pts/1    S+    16:12 /usr/bin/python /srv/system-image.ubuntu.com/bin/copy-image trusty-proposed trusty mako 226 -k10:52
didrocksso, we'll need stgraber?10:52
ogra_runs sine 16:1210:52
ogra_yes, i think so10:52
ogra_seems copy-image also doesnt produce any logs10:52
ogra_it just sits there (seems to be in running state though)10:53
cjwatsonmight just be rechecksumming or something10:53
ogra_i see it updated the timestamp for the output dir though10:53
cjwatson29071 pts/1    S+    16:14  |                   \_ /usr/bin/python /srv/system-image.ubuntu.com/bin/copy-image trusty-proposed trusty mako 226 -k10:53
cjwatson 2963 pts/1    Rl+    0:33  |                       \_ pxz -z -9 -c /tmp/tmpgcbAS5/output.tar10:53
cjwatsonlooking at more of the process tree helps :P10:53
ogra_sigh ... we have 6 arches to promote10:53
cjwatsonI'm sure it'll get there10:53
ogra_that will take 1.5h now10:53
cjwatsonxz compression just takes a while10:54
ogra_yeah, but it used to be a matter of 1-2min before10:54
cjwatsonthen why will it take 1.5h now?10:54
cjwatson1-2min * 6 != 1.5h10:54
ogra_i guess that we havent promoted anything in rwo weeks might play a role for the diffing10:54
ogra_cjwatson, it used to take 1-2min ... if it takes 15 per arch now it will take a small century :)10:54
ogra_ah, it moved10:55
cjwatsondoes it matter for this particular run? :)10:55
Mirvcjwatson: ok doesn't start too well https://launchpadlibrarian.net/168944721/buildlog_ubuntu-trusty-arm64.qtbase-opensource-src_5.2.1%2Bdfsg-1ubuntu6_FAILEDTOBUILD.txt.gz10:55
ogra_not anymore, no ... i would have waited with starting it though ... since i have to go afk in 10min10:55
Mirvthe patches that were there with 5.0.2 were http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtbase-opensource-src/revision/14010:55
cjwatsonogra_: it got through manta pretty quick, so *shrug*10:56
ogra_oh, seems the other arches run faster10:56
cjwatsonMirv: so what thinks it needs to use -m64?10:56
ogra_grr10:56
ogra_http://paste.ubuntu.com/7067002/10:56
cjwatsonMirv: oh right, easy10:57
cjwatsonMirv: http://paste.ubuntu.com/7067006/10:57
cjwatsonthat's for arches where -m64 doesn't make sense10:58
Mirvcjwatson: ok, and I don't see other similar things in debian/rules so I guess worth a rerun unless there's a test PPA to use10:59
cjwatsonyou used to have a separate if case for it, you just moved arm64 to the wrong place10:59
cjwatsonhttp://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtbase-opensource-src/view/140/debian/rules lines 69-7211:00
davmor2Morning all11:00
cjwatsonMirv: probably worth just rerunning in 00611:00
Mirvok11:00
mandelogra_, do you know how is the qt 5.2 thing going?11:02
ogra_mandel, Mirv does ;)11:02
Mirvmandel: https://bugs.launchpad.net/webbrowser-app/+bug/1207270 needs to be fixed and some AP tests are failing http://q-jenkins:8080/job/autopilot-release-gatekeeper/63/11:03
ubot5Ubuntu bug 1207270 in Ubuntu UI Toolkit "Font size too small in browser with Qt 5.1 / DPR rework" [Critical,In progress]11:03
mandelMirv, thx11:03
ogra_mandel, Mirv does ;)11:04
ogra_oops11:04
ogra_sorry11:04
MirvI do, I do11:04
ogra_heh, EFOCUS11:04
Mirvand that's why I've prevented 'up' binding in irssi, requiring ctrl-up11:04
* ogra_ needs to go afk now for like 20min ... i'll check the promotion later ... looks like mako might need a re-run 11:06
mandelMirv, we need to fix that ogra_ bot, it has some weird stammer11:06
ogra_heh11:07
tvosssil2100, ping11:15
tvosssil2100, any luck with the dbus-cpp packages?11:16
tvosssil2100, didrocks can I get a silo for line 34?11:16
didrockstvoss: unity-mir is part of the qt 5.2 landing11:17
tvossdidrocks, oh okay11:17
sil2100tvoss: still checking out - looks ok from the outside, but I still couldn't get location working yet11:18
tvosssil2100, location not working as in?11:19
sil2100tvoss: can't force webbrowser to use location data after enabling it in the indicator11:23
sil2100popey, davmor2: does location work properly for you on stock 229 ?11:24
tvosssil2100, the indicator is not fixed with my changes. Also: it might take 15 minutes to acquire a fix11:24
popeysil2100: define "work"11:24
sil2100popey: after enabling the indicator, does opening a webbrowser prompt you for allowing location on google maps and then it finally finds the GPS signal?11:26
popeysil2100: i have _never_ had success in a browser finding location11:26
davmor2sil2100: haven't tried it yet, ignore the indicator though it lies11:26
popeytell you what is odd though11:27
popeyopen browser, visit maps.google.com, kill browser, start again.11:28
popeyThe first time you get mobile version of gmaps, second time you get desktop version11:28
davmor2popey: because you click on the link for maps right11:28
davmor2popey: -https:// always links to the mobile site, if you click on the link it the address bar it always goes to desktop11:29
ogra_hmm, so promoting mako and generic failed ... re-running for these two11:31
popeyno11:32
popeyi didnt click any link11:32
popeyi opened browser11:32
ogra_ugh, and flo too ...11:33
* ogra_ sighs11:33
davmor2sil2100: osmtouch has me pinpointed nicely so I assume gps is working11:34
popeydavmor2: osmtouch doesn't use gsm11:38
popey*gps11:38
davmor2popey: It's stops flashing the warning there is no gps and pinpoints you precisely when there is a fix and google maps works then too11:39
davmor2popey: initially it doesn't I agree but then it tells you it isn't using gps and also tells you that the position is approximate11:41
davmor2popey, didrocks, ogra_: screen has just frozen again, this time 2 apps open and I swiped to get back to the dash chasing up on #ubuntu-mir channel but not seeming to get a response yet,  I'll carry on dogfooding on the n7 for a bit11:45
didrocksdavmor2: thanks11:45
ogra_davmor2, make sure to back up syslog and the output of dmesg ... and probably also logcat11:46
davmor2ogra_: thanks will do that now, the phone is working fine just not the screen11:47
ogra_right11:47
popeydavmor2: Mar 10 11:47:38 ubuntu-phablet com.ubuntu.location[893]: SV status update: [#svs: 23]11:47
popeyi get 23 satellites in view and it still cant get a lock11:47
ogra_syslog should show OOM if there is any OOM going on ... and logcat should show any graphics driver issues11:47
davmor2popey: just checked top and there is no swap being used so it's not the issue you saw11:48
popeyit takes a long time to use swap11:48
popeyyou need an app to be open for hours11:48
davmor2popey: ah okay so no :)11:49
sil2100tvoss: didn't test location properly yet but all seems to be ok I think11:51
ogra_sigh .... and generic failed again ... as did flo11:51
sil2100Let's publish (again)11:51
* ogra_ re-runs again with these two arches11:51
didrocksogra_: keep logs for Stéphane I guess11:53
didrocksogra_: btw, as mako is promoted, it's now show up as promoted on the dashboard :p11:53
ogra_yeah, indeed11:54
popeydavmor2: for me, it always says no gps11:58
davmor2popey: let me get it install on the n711:59
=== josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Landing instructions: http://goo.gl/8H1Du3. Landing in degraded mode (see http://goo.gl/J1EqPW)
sil2100didrocks: http://162.213.34.102/job/landing-003-2-publish/lastSuccessfulBuild/artifact/packaging_changes_dbus-cpp_2.0.0+14.04.20140310-0ubuntu1.diff <- packaging change ;)12:12
tvosssil2100, ack and thx12:12
tvosssil2100, I got a fix here, standing on the balcony and waiting for ~8 minutes12:13
didrockssil2100: looks good to me12:13
sil2100didrocks: thanks ;) Let's see how it goez12:19
davmor2popey: this is all I get once I have a lock http://ubuntuone.com/4HwOplWn8pgR3yWMU1Hq7e until then it shows me in bushbury about a mile and a half away and says it's a guess :)12:23
sil2100didrocks: so, can I now publish only one component that was re-built? Since I rebuilt only dbus-cpp, publish job says that others (platform-api and location-service) weren't rebuilt - can I safely tell him to ignore those and just push dbus-cpp out? No need to re-release the others, no changes or rebuilds required there12:25
didrockssil2100: yeah, just use the ignore flag12:26
popeydavmor2: how do you know when you have a gps lock?12:26
sil2100*click*12:26
davmor2popey: I keep clicking on the My location button either in maps.google.com or osmtouch till it is right :)12:27
sil2100didrocks: all seems to work fine! o/12:28
didrocks:)12:28
ogra_didrocks, so i promoted on all arches now manually bit by bit ... sald yi messed up on flo so that it is called 207 there ... will sort that ut once stgraber is up12:28
didrocksogra_: ok, thanks a lot! :)12:28
davmor2popey: maps.google.com tends to show position correctly when osmtouch does though up until then it says no gps location or words to that effect12:29
ogra_smells like the import job that runs every 5 min to check for new cdimage files makes it fall over ... once i disabled it i could at least run copy-image manually for each arch12:29
didrockssil2100: as you can see, it's tracking the right version of dbus-cpp12:36
=== alan_g is now known as alan_g|lunch
cjwatsonMirv: looks like qtbase/arm64 is good now13:01
Mirvcjwatson: yes, I was just refreshing Packages file and starting landing the rest of the Qt modules13:02
Mirvdone, qtxmlpatterns started already13:05
sergiusensdidrocks, hey, for new packages that would be handled by ci train; how do we do the ffe?13:17
didrockssergiusens: it's packages that are new to the archive?13:18
sergiusensdidrocks, yup13:18
sergiusensdidrocks, media-hub to be specific13:18
sergiusensand this is also a request to get that in :-)13:18
didrockssergiusens: it needs a regular FFe, then, we just handle it as any new package (so either an empty MP to get it landing or an existing one)13:20
didrockssergiusens: you can file the request first in, but please add to the comment that it needs the FFe to be acked13:20
didrockstvoss: you can merge and clean btw13:26
tvossdidrocks, okay13:26
cjwatsonMirv: https://launchpad.net/~ci-train-ppa-service/+archive/landing-006/+build/5798790 looks like a proposed-migration blocker13:52
plarsdidrocks: we have an issue with the ubuntuuitoolkit tests - on mako there seems to be an issue where it sometimes runs forever (until the job times out after 300 min)13:52
didrocksplars: oh, interesting, we didn't get any change on the toolkit for that. Is that quite new?13:52
didrocksbzoltan1: you may have some people too look at that ^13:52
plarsdidrocks: ah, wait13:53
plarsdidrocks: maybe a false alarm - it looks like it's still on just the custom image13:53
plarsdidrocks: for a second I saw that mako was still running and thought we were seeing the same thing on the regular images13:53
didrocksinteresting…13:55
didrocksplars: keep us posted :)13:55
plarscwayne was looking into it on custom but if anyone has ideas, could probably use some help13:55
tvossdidrocks, can I just press merge and clean in the silo?13:55
bzoltan1didrocks:  let me look at it13:57
didrockstvoss: yeah13:57
didrocksbzoltan1: apparently, cwayne will be your best contact :)13:58
tvossdidrocks, without setting any options I assume?13:58
bzoltan1plars: please ping me and paste the logs if you suspect the ui toolkit doing something wromg13:58
didrockstvoss: right, no option13:58
=== alan_g|lunch is now known as alan_g
cjwatsonMirv: http://paste.ubuntu.com/7067776/ should fix https://launchpad.net/~ci-train-ppa-service/+archive/landing-006/+build/5798788, or at least move onto the next thing - not a proposed-migration blocker but would be awfully nice14:05
Mirvcjwatson: there was a recent 5.0.2 patch that didn't apply but it seems it can be made to apply.14:07
Mirvcjwatson: this applies http://pastebin.ubuntu.com/7067786/14:07
Mirvcjwatson: so maybe I'll apply both?14:08
cjwatsonMirv: aarch64.patch already has a definition of WTF_CPU_ARM64 (you could pick either but there's no reason to change the existing patch really)14:11
cjwatsonMirv: and I think it's probably better to match the style of the code the patch would be applying to, which is all __foo__ macros rather than CPU(foo)?14:12
cjwatsonMirv: it's certainly the same idea though14:12
cjwatsonMirv: if qtwebkit doesn't have that yet, it'll probably need it too, though14:12
cjwatsonI suppose you might need to care about CPU(ARM64) vs. CPU(AARCH64) if that's exported to other packages; I don't know whether that's so14:13
cjwatsondoesn't really matter which, pick one :-)14:14
Mirvcjwatson: which aarch64.patch already has WTF_CPU_ARM64? so what I pasted is from https://launchpad.net/ubuntu/+source/qtscript-opensource-src/5.1.1+dfsg-2ubuntu1~really5.0.2+dfsg-3ubuntu1 modified to apply to 5.2.1 qtscript14:21
cjwatsonMirv: the one you currently have in qtbase14:21
cjwatsonMirv: sorry, in qtdeclarative14:22
cjwatsonwhich I ported over from webkitgtk14:22
cjwatsonwe've apparently used different names in different places, shrug14:22
Mirvoh, there!14:22
Mirvright14:22
cjwatsonprobably ought to be consistent within qt* at least :)14:23
Mirvcjwatson: another problem is that qtdeclarative failed to build on arm64, which wouldn't be a problem otherwise but it's nowadays required by qttools which did build on arm64 before..14:23
davmor2didrocks: things look okay on the n7 I still need to get my n4 unlocked and it looks like the first of the people who maybe able to help me is now online14:24
cjwatsonMirv: that was what I gave you the patch above for, http://paste.ubuntu.com/7067776/14:25
didrocksdavmor2: excellent! good luck and cross fingers :p14:25
pmcgowandidrocks, are you considering a change to the landings order given Qt is still getting fixes14:25
didrockspmcgowan: you mean, order like 1, 2… 3 or anything else?14:26
Mirvcjwatson: ahah, I mistakenly thought it was reated to qtscript first you mentioned earlier. ok, let's see.14:26
pmcgowandidrocks, like landing mir and scopes before qt for example14:26
didrockspmcgowan: basically everything that are not in Qt "lock list" can enters14:26
pmcgowandidrocks, cool14:26
didrockspmcgowan: Mir will be blocked I guess because of unity-mir though14:26
didrocks(it's in the Qt lock list IIRC)14:27
pmcgowanmaybe it can get unlocked for the time being14:27
didrockspmcgowan: totally fine with that, it's just a rebuild for Qt?14:27
didrocksLet me check14:27
pmcgowannot sure14:27
cjwatsonI might try another click landing to get a bit more of libclick (manifest extraction and the supported framework stuff)14:27
cjwatsonsqueezing that in before Qt would be good14:27
pmcgowanthat would be good14:27
pmcgowan+114:27
didrockspmcgowan: ok, so unity-mir is just a rebuild14:29
didrockspmcgowan: we can easily stick it out, get Mir landing and stick it back14:29
pmcgowandidrocks, great14:29
didrocksjust Mirv needs to do a manual tracking to remember to rebuild it once Mir is in :)14:29
pmcgowanyep14:29
pmcgowanwe did that with eds the other day as well14:29
didrocksyeah, that's easy to do, just need to not forget about it in the bazillon packages :)14:30
didrockskgunn: you want to make a Mir landing tentative?14:31
kgunndidrocks: yes!14:32
kgunnthankyou!14:32
didrockskgunn: the line request is up to date?14:32
didrocksMirv: mind if I remove unity-mir from you, as discussed? ^14:33
ogra_=== Image 226 promoted ===14:33
ogra_(now including all arches etc)14:33
pmcgowannice14:34
didrocksogra_: great!14:34
ogra_so the long tarball genersation due to the diff being gigantic after two weeks was the issue14:34
ogra_it caused some "stepping on my own toes" in the tools14:34
balloonswahoo!14:35
didrockskgunn: ready is set to "No", on purpose?14:35
davmor2\o/ \o/ \o/14:37
sil2100\o/14:39
didrocksMirv: unconfigured unity-mir then14:39
didrocksah, will need to unconfigure u-s-c as well14:40
didrockssil2100: Mirv: ok, I unlocked unity-mir and unity-system-compositor Qt 5.2 landing. I kgunn ack the Mir landing line, please assign to him14:44
* didrocks is going for a run now14:44
kgunndidrocks: sorry...was in a meeting14:49
* kgunn looks to catchup14:49
rsalvetipopey: have a bug number for the emulator issue?14:49
rsalvetipopey: downloading the latest and will check14:49
popeyrsalveti: tried multiple times and got black screen first few times then it worked the last time annoyingly14:49
kgunndidrocks: fixed the sheet14:49
rsalvetipopey: alright, guess just the usual issue with qemu not bringing up everything sometimes14:53
rsalveticjwatson: Mirv: not sure if helps, but marcin had a few arm64 patches for qt5.2 as well: https://bugzilla.redhat.com/show_bug.cgi?id=1056051 https://bugzilla.redhat.com/show_bug.cgi?id=1056071 https://bugzilla.redhat.com/show_bug.cgi?id=105616014:54
ubot5bugzilla.redhat.com bug 1056051 in qt5-qtdeclarative "Add AArch64 support to qtdeclarative" [Unspecified,Closed: rawhide]14:54
ubot5bugzilla.redhat.com bug 1056071 in qt5-qtscript "Add AArch64 support to qtscript" [Unspecified,Closed: rawhide]14:54
ubot5bugzilla.redhat.com bug 1056160 in qt5-qtwebkit "Add AArch64 support to qtwebkit" [Unspecified,Closed: rawhide]14:54
cjwatsonprobably similar/overlapping14:56
rsalvetiyeah, at least the last 2 are already upstream as well14:57
sil2100didrocks: ok14:58
rsalvetidavmor2: popey: did we have a bug for the delay when enabling/disabling speaker mode?15:03
rsalvetisil2100: didrocks: thanks for creating the silo for 46 btw15:03
kgunnMirv: sil2100 ...can you reconfig silo2 ? i add one more MP back into the list15:03
sil2100kgunn: ok15:04
sil2100rsalveti: no problem15:04
davmor2popey: did we modify your original sound loud speaker doesn't work bug?15:05
sil2100kgunn: can I reconfigure already or are you still adding?15:05
kgunnsil2100: yeah, sorry, just hit enter...now try :)15:05
popeydavmor2: my what?15:05
sil2100;)15:06
davmor2popey: you filed a bug for loud speaker not working did we modify that when both of us got it to work but delayed?15:07
popeypass15:07
pmcgowandavmor2, there is a bug on the delay, forget against which package15:08
davmor2rsalveti: ^15:08
davmor2pmcgowan: thanks I thought there was too :)15:08
rsalvetipmcgowan: remember the number?15:08
pmcgowanrsalveti, not off hand, I can look15:09
davmor2rsalveti: more than 1, less than a billion, does that help lower it down?15:09
rsalvetidavmor2: not much lol15:09
pmcgowanrsalveti, davmor2 https://bugs.launchpad.net/dialer-app/+bug/127776515:10
ubot5Ubuntu bug 1277765 in dialer-app (Ubuntu) "big delay when pressing speakerphone icon on N4" [High,Confirmed]15:10
rsalvetipmcgowan: awesome, thanks15:10
davmor2pmcgowan: thanks15:11
rsalvetipmcgowan: davmor2: popey: mind help testing https://launchpad.net/~ci-train-ppa-service/+archive/landing-001/ ? (alsa-lib, fix the delay when enabling/disabling speaker-mode)15:37
rsalvetididrocks: sil2100: guess I also need someone from the ci team to give it a try as well :-)15:37
davmor2rsalveti: I'm working on my issue with mir right now.15:38
cjohnston/3/1715:40
sil2100rsalveti: what's up?15:44
sil2100rsalveti: the alsa one?15:44
sil2100:)15:44
rsalvetisil2100: yes15:48
bregmasil2100, could I get a silo for line 42 please?16:00
sil2100bregma: let me take a look16:01
seb128bregma, sil2100: you probably want "gnome-screensaver" in the column G16:02
sil2100bregma: is the FFe accepted? Can you point me to the bug?16:23
cjwatsonMirv: at least qtdeclarative is down to tedious symbols stuff now ...16:26
cjwatsonso close :)16:26
bregmasil2100, FFe bug is https://bugs.launchpad.net/unity/+bug/128279816:29
ubot5Ubuntu bug 1282798 in Unity "[FFe] Provide a lock screen and unlock dialogs in Unity" [Medium,In progress]16:29
bregmabeing review still, obviously we won't land the silo before it's approved16:30
sil2100bregma: right, I didn't see a Triaged yet16:33
sil2100bregma: is it important that we have it built for the FFe to be reviewed?16:33
bregmasil2100, better to ask Laney16:35
LaneyYou can build it, that allows for testing16:35
Laneyjust don't put it in trusty16:36
sil2100Laney, bregma: I'll assign a silo and mention it in the comment16:36
sil2100Damn, good that CITrain is smart!16:40
kgunnsil2100: hey...would you be the right person to approve/add...the following16:41
kgunnhttp://summit.ubuntu.com/uds-1403/kgunn72/meetings16:41
sil2100Oh, shock, it seems I do have the power16:42
sil2100bregma: assigned a silo, you can build ;)16:48
rsalvetipmcgowan: sil2100: landing 46 (https://launchpad.net/~ci-train-ppa-service/+archive/landing-001) is working as expected, would just like someone else to give it a try before getting it published (as we're in degraded mode)16:49
sil2100rsalveti: upgrading on my device16:49
rsalvetigreat16:49
sil2100rsalveti: did most of the testing from the testing plan and I think it seems ok17:00
popeydidrocks: "You're not allowed to join this video call."17:00
ogra_popey, use the right account then :P17:01
* ogra_ has to wrangle with that once a week 17:01
popeyi am17:01
didrocksweird…17:01
popeyi use two browsers17:01
rsalvetisil2100: great, can we land it already? or should we wait17:01
* popey invited himself to the meeting17:02
davmor2didrocks: https://bugs.launchpad.net/mir/+bug/129041617:04
ubot5Ubuntu bug 1290416 in Mir "Mako locks up roughly once a day since R226" [Undecided,New]17:04
rsalvetidavmor2: wonder if this might be the issue that was fixed for mwc17:07
rsalvetikgunn: should know more17:07
rsalvetibut I know we had a screen freeze there as well17:07
sil2100rsalveti: oh, you forgot to push 'build' with 'watch only' for the silo ;)17:08
sil2100rsalveti: want me to do that?17:08
kgunndavmor2: mir hasn't changed since ~Feb2017:10
kgunndavmor2: does your image include Qt5.2 ?17:10
kgunn(sorry i need a decoder ring :)17:10
davmor2kgunn: no17:10
davmor2kgunn: kdub and AlbertA are happy that they have starting point on that bug now17:11
kgunnack...17:12
davmor2kgunn: this has only been happening since R22617:12
davmor2kgunn: which is the promoted image from Friday17:12
kgunndavmor2: hmmm...what was big landing there ? anyone know ?17:13
davmor2kgunn: pretty much everyone now but I've not long finished adding all the debug stuff to the bug for your guys to work with :)17:14
ogra_plars, could someone look at the messaging-app tests on the tablets ? it looks like ofono-phonesim is not installed when they run17:14
davmor2kgunn: hence giving didrocks the bug number for the daily release report ;)17:14
kgunndavmor2: ack...just trying to square what you are describing as a "mir regression"..but we haven't released a new mir :)17:15
kgunnAlbertA: kdub ^17:16
sil2100rsalveti: I'll do it then and publish17:16
davmor2kgunn: no not a regression but it has only been noticeable since R226  :)17:16
AlbertAkgunn: yeah it's still 0.1.517:16
AlbertAkgunn: areas of suspect from the logs are snapshooting17:17
AlbertAkgunn: and a possible deadlock during sessionDestroyingSurface17:17
kgunnAlbertA: ah...so this is the old mwc bug17:18
AlbertAkgunn: oh this was known?17:19
kgunnAlbertA: yeah...but just hung up on "process" itself :)...its fixed on dev17:20
davmor2kgunn: ah cool :)17:20
bregmasil2100, I don't see a silo for line 42 no matter how many times I refresh, did I miss something?17:24
robrukgunn, just checking in. I'm all yours for the next 8 hours if you need any help with the Mir landing.17:28
kgunnrobru: thanks...working on damn mp conflicts now!...arg17:29
robrukgunn, yeah, i noticed that ;-)17:29
=== Ursinha is now known as Ursinha-afk
sil2100didrocks: ok, so it seems cyphermox freed the silo17:34
sil2100bregma: ^17:34
didrockssil2100: yeah, what I told you, I guess he did this because of the unack FFe17:34
sil2100cyphermox: so, Laney as the reviewer of the FFe approved the assignment of the silo for testing purposes17:34
Laneyhaha17:35
LaneyI don't want to be known as 'the reviewer' please17:35
sil2100cyphermox: I made the comment red to make sure it doesn't land before ACKing the FFe itself17:35
Laneyanyone on the RT can look at any request17:35
LaneyI just think it's sensible to be able to test it17:35
sil2100Laney: ok ;) But I saw you being the most active on that bug17:35
cgoldbergrobru, cyphermox, any chance of getting a silo allocated for line 47 today? (Autopilot)17:36
sil2100cyphermox, didrocks: you think we can re-add that silo, or you want to leave it unassigned?17:36
cgoldbergi was unable to make landing meeting earlier17:36
robrucgoldberg, I can assign it17:36
sil2100It's fine either way for me, but as Laney mentioned, it might be easier to test for people actually17:36
cgoldbergrobru, great thanks17:37
didrockssil2100: please readd17:37
didrocksrobru: try to decouple the Mir and autopilot landing please17:37
robrudidrocks, yes ;-)17:37
didrockslike having an image just with one, and an image with the other17:37
didrocksthanks!17:37
robrucgoldberg, yeah, I have to try not to land mir and autopilot too close together17:38
didrockscgoldberg: I don't think autopilot-qt though17:38
didrockscgoldberg: remember that both autopilot and autopilot-qt were reverted17:38
robrucgoldberg, ok you got silo 5, please build17:38
didrocksdue to the regression17:38
didrocksare they fixed?17:38
sil2100cyphermox: ^ please don't unassign for now ;)17:38
cgoldbergdidrocks, yes afaik17:39
didrockscyphermox: apparently, the release team wants to test built packages before +1 or -117:39
didrockscgoldberg: so, why autopilot-qt isn't part of the landing?17:39
cgoldbergdidrocks, one sec.. let me go through email and see whats up with autopilot-qt17:40
didrocksrobru: please don't release before this is cleared out ^17:40
robrudidrocks, ok. i plan to do mir first anyway17:40
sil2100bregma: the silo is back - silo 008 now17:41
sil2100Ok guys, I drive home now - see you around!17:41
robrusil2100, good night!17:41
didrockssee you sil2100 :)17:41
* didrocks waves good evening as well now17:45
didrockscgoldberg: keep us posted on the ML as well (the whole LT)17:45
didrocksthanks17:45
=== bfiller is now known as bfiller_afk
=== Ursinha-afk is now known as Ursinha
rsalvetikgunn: davmor2: it's probably related with 4.417:54
rsalvetikgunn: that's why I said it should be similar with the issue we had with the mwc demo image17:54
rsalvetiso the only thing that changed is the hwcomposer17:55
rsalvetias it's using a different version now, so mir might still have issues with it (hwcomposer 1.2)17:55
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Landing instructions: http://goo.gl/8H1Du3. Landing in degraded mode (see http://goo.gl/J1EqPW)
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Landing instructions: http://goo.gl/8H1Du3. Landing in degraded mode (see http://goo.gl/J1EqPW)
sergiusensrobru, can I get a silo for l50?18:02
robrusergiusens, sure18:03
davmor2rsalveti: that's fine if there is already a fix that is awesome :)18:03
davmor2rsalveti: if all my logs and everything provided was confirmation that the bug is the same then it doesn't feel like a complete waste of a day :)18:04
robrusergiusens, ok, you got silo 9, please build18:04
rsalvetidavmor2: sure18:04
sergiusensty18:04
robruyou're welcome!18:05
=== alan_g is now known as alan_g|EOD
sergiusensrobru, one more for l51 if you don't mind18:09
robrusergiusens, is the py3 stuff backwards compatible? or are you breaking py2 there?18:10
sergiusensrobru, it's backwards compatible18:10
robrusergiusens, great ;-)18:10
sergiusensrobru, but; that's why we need to run agains everything currently under the ci image test anyways to make sure18:11
robrusergiusens, right18:11
robrusergiusens, ok, you got silo 10, please build18:11
sergiusensI intend to ping doanac` for that; tsk :-)18:11
robruseb128, do you need me to publish silo 7? I forget if you can publish or not18:12
seb128robru, just did, thanks18:12
robruseb128, great18:12
davmor2psivaa, plars: you guys around now?18:14
psivaadavmor2: hello18:14
plarsdavmor2: yes18:15
davmor2psivaa, plars: If you are both about could we have a 5 minute hangout?18:15
plarssure18:15
davmor2psivaa, plars: https://plus.google.com/hangouts/_/7ecpj08l3ar12lr9julchs3cvc?hl=en-GB18:16
plarsdavmor2: it says I'm not allowed to join18:17
davmor2plars: it's a canonical one18:17
kgunnsorry...had some internet monkey biz... davmor2 kdub AlbertA rsalveti ...the free bug is this one, and has a fix in 0.1.6...which i'm trying to land right now18:18
kgunnhttps://bugs.launchpad.net/ubuntu/+source/unity8/+bug/128172818:18
ubot5Ubuntu bug 1281728 in unity8 (Ubuntu) "Unity8 random freeze on demo image" [Critical,In progress]18:18
plarsdavmor2: I'm logged into two accounts - it's never been a problem before though18:18
davmor2plars: :(18:18
davmor2psivaa: is in so I don't know what the issue is18:19
davmor2plars: ^18:19
plarsdavmor2: give me a sec18:19
davmor2kgunn: fantastic so when the new version lands everythign should be back to normal then right?18:19
plarsdavmor2: can you invite me?18:20
kgunndavmor2: unless its a new bug...in which case all my wonderings about no-new-mir are meaningful :)18:20
rsalvetikgunn: are we still trying to land mir before qt 5.2?18:22
kgunnrsalveti: so i have mir building in silo 002 atm18:22
kgunni know 5.2 is special...so not completely sure how to answer your question :)18:23
robrursalveti, oh yes, the plan is to land mir today, and qt5.2 "sometime this week" (when it's ready)18:23
kgunnrobru: so..i just lost console on silo002....but i assume the build is still going ?18:24
kgunnclicking on console view give me a "service temporarily unavailable"18:24
sergiusensrobru, I just got a 503 from jenkins/train, is it only m?18:24
robrukgunn, dear god...18:24
sergiusensah18:24
sergiusensnot only me then...18:25
robrukgunn, your builds are still here: https://launchpad.net/~ci-train-ppa-service/+archive/landing-002/+packages18:25
rsalvetigreat then18:25
robrunot sure where jenkins wentthough18:25
robrucyphermox is the only person who has the access to fix this at this time of day.18:25
sergiusensdoanac`, can you run https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc&usp=drive_web#gid=28 with utah/ci?18:27
doanac`sergiusens: ack.18:29
sergiusensdoing the same, but without utah18:31
kgunnrobru: so...looks like none of those packages actually published18:31
kgunnfailed on dep waits...18:31
robrukgunn, amazing18:31
robrukgunn, how did they both fail? the ppa build should not be affected by jenkins going down (jenkins just monitors the builds, they are standard PPA builds handled by launchpad)18:32
doanac`sergiusens: NOTE: we aren't using utah for touch testing anymore, but i'm still running it through our ci scripts here: http://q-jenkins:8080/job/andy-smoke-daily-test/3/console18:32
kgunnrobru: gotta run for lunch...bbiab18:34
sergiusensdoanac`, oh, interesting; thanks for the detail18:35
robrukgunn, so lp:mir never got uploaded to the silo.18:36
robrukgunn, and therefore everything that depended on it is stuck in depwait18:38
robrukgunn, i am literally powerless to fix this until cyphermox gets here to reboot jenkins. he just told me he'll be available in a few minutes though18:39
cyphermoxjust started jenkins19:04
cyphermoxsorry, I was stuck in traffic19:05
cyphermoxrobru: kgunn: jenkins is back up19:06
robrucyphermox, thanks19:17
robrukgunn, i started a rebuild for you19:21
thomirobru: cyphermox: are one of you two gentlemen able to explain to me why this build job failed please? http://162.213.34.102/job/landing-005-1-build/57/console19:31
robruthomi, checking19:31
thomiThere's a 'warning' message at the end of the console, but since it's a warning (and not an error) I'm not sure if that's why the build failed19:31
thomialso, the message doesn't make sense to me at all19:31
thomiI think maybe it's due to didier's reverting the package in distro19:32
robruthomi, yep, that warning is exactly why it failed.19:32
robruthomi, and also yes, a revert in distro would cause that.19:32
thomiok - that message *really* should be an error then... but anyway... how do I fix it?19:32
robruthomi, so what you need to do is grab the debian/changelog from distro and just copy that changelog entry into one of the MPs for the project, then once changelog matches distro then the build will proceed19:32
thomirobru: OK, gotchya, thanks.19:33
robruthomi, you're right though, it's weird that it's just a warning but then it fails on that... should be an error19:33
* thomi adds this bit of information to his ci-train manual19:33
robrursalveti, seb128 : hope I'm not stepping on your toes but I merged silos 1, 3, and 7 for you.19:35
rsalvetirobru: that's fine, thanks19:35
robrusergiusens, status is wrong in spreadsheet, silos 9 and 10 are both done building if you want to start testing19:37
sergiusensrobru, yeah, started a bit back when I saw the ppa finished buildinf :-)19:39
sergiusensthanks btw19:39
robrusergiusens, you're welcome19:39
robruok, everything looks good for now as far as I can tell, I'm going to take lunch, should be back within an hour, feel free to ping me if you need anything.19:40
seb128robru, that's ok, thanks19:57
popey3619:59
popeybah19:59
bregmarsalveti, I need someone to upload a package to a silo and it looks like you're the only one around who can help at the moment ... willing?20:00
rsalvetibregma: sure, what's up?20:00
bregmarsalveti, I need http://people.ubuntu.com/~3v1n0/Lockscreen-GS/ uploaded to ppa:ci-train-ppa-service/landing-008 (after properly setting the release in d/changelog) if you could20:01
rsalvetibregma: sure, 1 sec20:03
rsalvetibregma: building20:09
bregmarsalveti, thanks20:12
bregmarobru, cyphermox, could I get a silo assigned to line 52 please?20:24
cyphermoxmost certainly sir20:24
cyphermoxbregma: landing-00120:28
bregmawoo hoo, thanks20:28
robruok, i'm back for landings now20:54
robrukgunn, just checking on mir, looks like the last rebuild i started failed due to a bunch of depwaits, but the good news is that mir itself got uploaded and built successfully. I suspect if we just force yet another rebuild, it should all work.20:58
kgunnrobru: yep...or target build unity-mir, papi, usc20:59
robrukgunn, right, we should start target building mir first ;-)20:59
kgunnrobru: yeah...its weird, i thot it should do it all in order of the MP's21:00
kgunne.g. mir mp is first21:00
robrukgunn, yeah, i thought that was the case as well, but when I looked deeper into it, it seems to only respect the order within projects (eg, multiple MPs against papi will get merged in the right order) but the actual order of projects is completely arbitrary. not even alphabetical, it looks like they're stored in a python dict and then uploaded in python-dict-access-order, which is essentially unpredictable21:02
dobeyseems like something needs to apply all the patches to everything in the silo, then generate a package build dependency graph, get the source package for each binary bulid-depends, and see if it is one of the things in the silo, and build things in the silo in the appropriate order according to the dep chain21:16
dobeybut that is incredibly complex to do :)21:16
robrudobey, yeah, easier would be if it just built them in the damn order that we put the MPs ;-)21:41
robrukgunn, how's testing mir going? need a hand?22:13
kgunnrobru: was just about to begin...but yeah, if you're interested...22:14
robrukgunn, yeah ;-)22:14
robrukgunn, so I just installed the silo contents on my mako, rebooted, and it won't boot. somewhat troubling...22:14
kgunnrobru: hmmm...that is no good...22:14
* kgunn gets a little worried22:14
robrukgunn, just gets stuck at the 'Google' screen with the little unlock icon22:14
robrukgunn, hummm, reflashing didn't fix it. bootstrapping now22:17
robrukgunn, any luck on your end?22:17
bregmarobru, do me a favour and find a silo for line 53 when you get the chance?22:26
robrubregma, webapps? my pleasure!22:26
robrubregma, ok, you got silo 322:27
bregmathanks muchly22:27
robruyou're welcome!22:27
robrukgunn, is it possible that simply installing all binary packages present in the silo can result in a broken system? is there a certain subset of packages I should be installing in order to test this properly?22:30
kgunnrobru: so you do have to have all those packages together for sure22:31
kgunnrobru: i gotta run... i forgot about family dinner...bbiab...22:31
robrukgunn, ok, i'll keep poking at it22:32
robrukgunn, I'm gonna take a wild guess and say that installing ubuntu-desktop-mir on the phone was probably a mistake ;-)22:32
robrukgunn, hummm, now I can get past the Google screen, but it just boots into a black screen now. pressing the power button visible toggles from "screen on but black" vs "screen off". can't get unity8 to appear22:40
robrukgunn, ping me when you're back. not sure how to proceed22:43
doanac`sergiusens: here are the results from running that phablet-tools branch: http://q-jenkins:8080/job/andy-smoke-daily-test/3/#showFailuresLink22:53
sergiusensdoanac`, yeah, was just seeing them22:53
doanac`not sure which failures you expected and which you didn't. music app seems to not have run at all22:54
sergiusensdoanac`, calendar is expected; I forgot we needed a new image build for that22:54
sergiusensdoanac`, and gallery unexpected but easy to fix in any case22:54
doanac`sergiusens: great. let me know, and I can re-run for you any time22:54
sergiusensdoanac`, thanks, and will do!22:54
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Landing instructions: http://goo.gl/8H1Du3. Landing in degraded mode (see http://goo.gl/J1EqPW)

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