/srv/irclogs.ubuntu.com/2014/06/17/#ubuntu-ci-eng.txt

kgunnrobru: i'm around in lieu of camako00:25
robrukgunn, I just wrote you an email ;-)00:25
kgunnweeee mail00:25
robrukgunn, long story short, mir is building ;-)00:27
kgunnrobru: yeah, i actually read (most of) the backlog....what a tangled web of gcc shennanigans00:28
slangasekkgunn, robru: I see mir built now on armhf00:49
slangasekso yes, temporary bug in gcc-4.9 which would have been much more temporary if the silos were using -proposed00:49
robruslangasek, so clearly we need to identify the stakeholders and determine why it was chosen to disable -proposed in the first place, and make a case for enabling it permanently00:51
slangasekrobru: yep, agreed; should we bring this up on tomorrow's landing team call?  or ubuntu-phone?00:56
ogra_PPAs are always defaulting to use -proposed00:57
robruslangasek, yep, the landing team call would be a good start. ultimately didier will been to be involved, beyond that I'm not sure who else (probably didier would know who else)00:57
ogra_we only had one occurence once where we explicitly disabled building from there when cjwatson recommended it to us to work around a breakage00:57
robruogra_, currently all silos have -proposed disabled00:58
ogra_and that silo was definitely set back to "normal" (i.e. use -proposed)00:58
ogra_ugh00:58
robruogra_, and I have no idea why, or who made that choice00:58
ogra_thats wrong and not desired ... i'm sure that sil2100 wasnt the one changing the default00:58
ogra_he knows we need to build with it enabled00:59
robruogra_, last week I came close to enabling -proposed for all silos but backed down at the last second because i wasn't really sure what I was doing, or why it was set that way00:59
ogra_slangasek, robru, i'll carry it into tomorrows morning meeting00:59
slangasekok00:59
slangasekI think we need to understand who made this change and why; will the right people be in the meeting to answer that question?01:00
ogra_i know that i set ppa-19 back to use proposed when we did the workaround ... and i see it still has that setting01:00
robruslangasek, well, there's a good chance that anybody related to citrain will be in that meeting. except for didrocks and asac, they won't be there and they might know something01:00
ogra_well, sil2100 should definitely know who changed it01:01
ogra_i dont thinnk asac knows or cares ... but didier might01:01
ogra_he will be online to ask at least ... even if he doesnt come to that meeting anymore01:01
ogra_looking through the current PPAs it seems rather random01:02
ogra_18 and 19 both build with proposed01:03
ogra_17 doesnt01:03
robruogra_, I just enabled 16 and 18 today to workaround a failing build on arm01:03
robruogra_, but last week when I was looking at this, they all had -proposed disabled01:03
ogra_robru, can you make sure it is enabled in all of them ?01:03
robruogra_, yeah I can do that01:03
ogra_thanks01:03
robruyou're welcome01:03
ogra_:)01:03
* ogra_ wonders why he is chatting at 3am and slowly sneaks bedwards :) 01:04
robruogra_, hm, did you do the first 10 already? somebody beat me to those ;-)01:05
ogra_nope, i didnt touch anything01:05
ogra_only looked01:05
ogra_(but from the other end)01:06
robruweird, so as of just now, 1-10, 16, 18, and 19 had them enabled, the rest were disabled. I enabled them all.01:06
robrubut last week, I think on thursday, they were definitely all off01:06
ogra_i know for sure it was on when we disabled it for silo 19 back then01:07
ogra_and i never checked the others01:08
robruogra_, did you somehow disable them all? ;-) I only know how to do it one at a time ;-)01:08
ogra_(assuming they would all use the same default)01:08
robruinfinity, slangasek : https://launchpadlibrarian.net/177744514/buildlog_ubuntu-utopic-armhf.unity-scope-click_0.1%2B14.10.20140616-0ubuntu1_FAILEDTOBUILD.txt.gz unity-scope-click still failed even after rebuilding with -proposed.01:08
ogra_can general landers change the setup ?01:08
robruogra_, I think you have to be in the ppa-service team (eg if you have upload rights to the silos)01:08
ogra_right01:08
robruogra_, https://launchpad.net/~ci-train-ppa-service/+members#active 11 suspects...01:09
slangasekrobru: ok; so one of the linkage failures is fixed, two still outstanding there01:09
slangasekI'll keep digging01:09
robruplus whoever can control ps-jenkisn...01:09
robruslangasek, thanks01:09
slangasekrobru: which silo is this in?01:09
robruslangasek, that one's from 1801:09
robruslangasek, https://launchpad.net/~ci-train-ppa-service/+archive/landing-01801:09
* robru EODish, still around if you need me though01:11
kgunnslangasek: thanks for the help01:37
imgbot=== trainguard: IMAGE 85 building (started: 20140617 02:05) ===02:04
kgunnslangasek: just for the conversation about building against proposed...although the packages built, they wouldn't install02:46
kgunnb/c the packages in the image don't match what's in proposed02:46
kgunn libmirclient7 : Depends: libstdc++6 (>= 4.9.0-7ubuntu1) but 4.9.0-6ubuntu1 is to be installed02:46
kgunn...i started to go down the install proposed pocket packages path...but think i'll just wait a bit02:47
robrukgunn, is that just for armhf? I guess you should enable proposed on the device to be able to install ;-)02:50
imgbot=== trainguard: IMAGE 85 DONE (finished: 20140617 03:30) ===03:29
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/85.changes ===03:29
slangasekkgunn: yes, installing them would then also require enabling -proposed04:16
Mirvsil2100: hey. I didn't publish the autopilot yet even though it's marked as tested. is there any background to that, or should we just publish it?07:16
Mirvdbarth: you've a branch, not MP, listed in that Chrome Extension07:17
dbarthuh07:17
dbarthMirv: ok, now does that play ;)07:20
Mirvok :)07:23
Wellarkrsalveti: bug #1329945 should be fixed in ofono, not indicator-network07:30
ubot5bug 1329945 in indicator-network (Ubuntu) "WWAN signal strength is reported lower than android in same location" [High,Confirmed] https://launchpad.net/bugs/132994507:30
Wellarkit's the ofono percentages that are reported wrong07:30
Wellarkit's ofono's job to scale whatever strenghts the modem reports to the range of 0-100 %07:31
* Mirv has "Binder_2" consuming 100% CPU and only Google logo :(07:36
Mirvfunnily the Binder_2 has pid that ps says is /system/bin/sensorservice instead07:37
=== psivaa-afk is now known as psivaa
asacslangasek: ogra_: to find the background story of -proposed in ci train, you need to check with didrocks07:45
asache is in -touch etc.07:46
sil2100hmmm07:52
asacsil2100: all good?07:54
asac:)07:54
sil2100asac: yeah, just had some hardware failures here (unrelated)07:58
sil2100Mirv: ok, I checked this landing, it's good to go - I'll publish it in a moment07:59
sil2100Damn, #85 was a lucky build07:59
sil2100thostr_: hi! I see you have silo 13 for the 'forward-port' of HUD and I don't see it being built :)08:03
sil2100thostr_: could you move that silo further please?08:04
thostr_sil2100: in process of testing this right now08:13
Mirvis anyone else having "only Google logo shown" today more than earlier? I did --wipe --bootstrap but after upgrading to Qt 5.3 and reboot I was with google logo and probably not related in anyway to 5.3. also after downgrading I can't get anything on the screen.08:15
Mirvinitctl gives "Unable to connect to Upstart: Empty address ''"08:15
Mirvhistorically I've seemed to end up in these situations occasionally, but this is a new record08:17
cjwatsonslangasek: I think the argument for -proposed was to have silos be landable in isolation rather than being tied up in complex transitions, but it's clearly a two-edged sword.  My preference for a way forward would be for the new "airline" engine to have a simple switch for whether to build with -proposed or not, defaulting to on; if you needed to land something quickly that you knew was otherwise going to be tied up in a messy ...08:54
cjwatson... transition then you'd turn it off08:54
ogra_cjwatson, the point was that seemingly the default was to have -proposed off ... which wasnt intentional but an oversight after utopic opened it seems08:58
ogra_(see #ubuntu-touch)08:58
cjwatsonogra_: Oh, interesting, I didn't know that was unintentional08:58
ogra_we used to have it on in trusty ... due to pre-release issues it was switched off apparently08:59
ogra_and forgottent to switch back ...08:59
ogra_-t08:59
=== chrisccoulson_ is now known as chrisccoulson
cjwatsonogra_: this is probably inevitable with any system where the setting isn't automatically maintained09:06
ogra_well, only a few people can change it and usually we dont touch the default09:06
cjwatsonYeah, but it ought to be reset automatically when reconfiguring09:07
ogra_yeah, thats true09:07
cjwatsonOtherwise drift is inevitable, in fact even more so because it's a rare thing people forget about09:07
cjwatsonHm.  Is this actually settable over the LP webservice?09:08
ogra_only for members of the owning team09:08
cjwatsonwell sure09:09
cjwatsonI just couldn't find the setting in the apidoc09:09
cjwatsonOh, it's the ArchiveDependency on the primary archive09:10
cjwatsonOK, yeah, that makes a degree of sense09:11
popey~/4809:14
popeybah!09:14
t1mpMirv: I installed landing-005 ppa with image 84, and now the device doesn't boot any more09:26
t1mpMirv: it reboots, but gets stuck on the Google screen.. on desktop I get a message that nexus 4 cannot be mounted. I can still adb to the device09:27
t1mpperhaps the qt5 in the silo is broken?09:27
brendandpopey, we have success09:41
brendandpopey, let's get it out there09:41
brendandpopey, i guess we should re-evaluate other tests suites that kill the keyboard and try and remove that (if they pass without it)09:42
ogra_++09:43
popeyawesome.09:43
popeybrendand: can you leave a comment on the merge please?09:43
oSoMoNsil2100, hey, would you mind publishing silo 12 for me?09:47
sil2100oSoMoN: sure, just got the ping :)09:47
sil2100Ok, I see it was +1'ed by Didier, publishing!09:49
Mirvt1mp: nope, the PPA is working but the gcc just broke, so when you upgraded you got that too09:55
t1mpMirv: this is weird right? http://pastebin.ubuntu.com/7657616/09:56
asacsil2100: will 84 be promoted?09:57
asac:)09:57
t1mpMirv: I tried to flash image 83 to fix it, but it still is stuck at the google screen, and /etc/ubuntu-build says I have image 84...09:57
sil2100asac: most likely! QA is doing dogfooding and we're assessing the translations issue09:57
asacthat would be fantastic. it has my pet bug fixed09:57
sil2100Pet bug? ;)09:58
Wellarkis this a known problem?10:00
ogra_sil2100, yeah, he is always evil to his pet bugs and wants to kill them :P10:00
Wellark/usr/lib/gcc/arm-linux-gnueabihf/4.8/../../../arm-linux-gnueabihf/libprocess-cpp.so: undefined reference to `std::__once_call@GLIBCXX_3.4.11'10:00
ogra_Wellark, where do you see that ?10:00
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train Status: #84 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
Wellarkogra_: silo builds10:04
ogra_which silo10:04
Wellarklike here: https://launchpadlibrarian.net/177764561/buildlog_ubuntu-utopic-armhf.dbus-cpp_3.0.0%2B14.10.20140617-0ubuntu1_FAILEDTOBUILD.txt.gz10:04
Wellarksilo 210:04
Wellarkhttps://launchpad.net/~ci-train-ppa-service/+archive/landing-002/10:04
ogra_hmm, that should have built ...10:05
ogra_Wellark, see #ubuntu-devel ... there is a new gcc and a new libstdc++10:05
ogra_might be related10:05
ogra_(tell doko please)10:05
sil2100Seeing all this I'm really getting more afraid of building a new image ;)10:06
Wellarkwell, seems that process-cpp is broken in the archive10:06
ogra_Wellark, please tell doko about it, seems ot be fallout of the new gcc10:07
ogra_(or rather libstdc++)10:07
sil2100Wellark: right, best if you poke on -devel about this10:07
sil2100Why is it so that everytime a new gcc appears we get breakages on all fronts10:07
ogra_well, it is hard to silo a new gcc and test against the whole archive :)10:08
ogra_we usually only get a new toolchain at the beginning of a release cycle though10:08
ogra_so you dont see that fallout as much10:09
=== vrruiz_ is now known as rvr
ogra_asac, wasnt your bug inside the gmail app ? you should be able to update that standalone10:20
ogra_(or was it in the webapp container ?)10:21
asacogra_: hmm. right. i haven't setup my ubuntu one because i couldnt update without it, but that works now, so guess i should go ahead10:24
Mirvt1mp: ok I should have a easier to do fix for you now10:26
davmor2ogra_, sil2100: oh new shinies look at dialer, messaging and contacts10:27
Mirvt1mp: if you unpack http://people.canonical.com/~tjyrinki/gcc/fix_gcc.tar to your phone and use dpkg -i *.deb , everything should work again (both with and without Qt 5.3)10:27
ogra_davmor2, yep, saw it ... pretty useless on my flo though :) ... but i saw the changelog and looked at the start pacges of the apps already :)10:27
davmor2ogra_: contacts isn't if you add irc nicks :D10:28
ogra_yeah, my flo gets re-flashed to often, i never set up the google syncing there10:28
sil2100davmor2: yeah ;) Yesterday they wanted to land a redesign of those, right?10:28
sil2100Too bad the UITK bits didn't land with tit10:28
sil2100*it10:28
sil2100(not tit)10:28
sil2100-_-10:29
davmor2sil2100: it landed they look pruetty10:29
ogra_yeah10:29
t1mpMirv: thanks! that did it http://pastebin.ubuntu.com/7657742/10:29
ogra_cant wait to actually see and use them on my phone10:29
Mirvt1mp: yeah. then if you need to dist-upgrade (eg. Qt 5.3 PPA or something), you need to dpkg -i *.deb those again afterwards (or one could use various other ways too of course)10:30
sil2100Oh, a downgrading tarball!10:30
* sil2100 goes for lunch10:43
popeyMirv: when you have a moment, could you please upload http://s-jenkins.ubuntu-ci:8080/view/click/job/filemanager-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.filemanager_0.3.205_armhf.click to the store?11:07
Mirvpopey: omg I feared for this day - the day something _changes_ so that I need to figure out the magic of click-toolbelt again. so, it might take some time.11:14
popeyoof11:14
MirvI've notes from the last time, when the official instructions was "do python setup.py install in a loop until it works"11:16
popeynice11:21
popeymaybe your cert timed out?11:21
popeyguessing now ☻11:22
Mirvpopey: my error is ImportError: cannot import name _compare_digest11:35
Mirvogra_: could you get https://code.launchpad.net/~timo-jyrinki/ubuntu-seeds/ubuntu-touch.utopic.fix_qtsensors/+merge/223389 in? it's blocking Qt 5.3 (found out only now that the Qt Creator / SDK got functional)11:36
Mirvpopey: done! https://bugs.debian.org/749491 's tip solved it for me (although I was unsuccessful in compiling/installing from a fresh checkout, the tip fixed the old installation dir)11:47
ubot5Debian bug 749491 in libpython2.7-dev "libpython2.7-dev hmac.py: cannot import name _compare_digest" [Normal,Open]11:47
ogra_Mirv, added and uploaded11:47
popeythanks Mirv !11:48
popeysil2100: file manager updated in store, /cc brendand11:49
sil2100!11:49
sil2100:D11:49
sil2100popey: \o/11:49
Mirvthanks ogra_!11:49
=== alan_g is now known as alan_g|lunch
sil2100Ok, I have to jump out to the dentist now...12:03
sil2100brb12:03
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #84 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
thostr_can anybody reconfigure silo 18?12:11
rsalvetiWellark: about bug 1329945, it shouldn't be fixed in ofono :-)12:18
ubot5bug 1329945 in ofono (Ubuntu) "WWAN signal strength is reported lower than android in same location" [Undecided,New] https://launchpad.net/bugs/132994512:18
rsalvetithere was a thread in upstream mailing list about this already12:18
rsalvetiit's not linear, and it's basically converting asu (1-31) to percentage12:18
rsalvetiWellark: we could change ofono to report asu instead, but then the same logic would apply in indicator-datetime12:18
rsalvetiWellark: and the tech specifics should also be handled in the client code12:20
thostr_is there anybody from the landing team online?12:20
rsalvetiWellark: https://lists.ofono.org/pipermail/ofono/2011-January/007827.html12:21
ogra_thostr_, Mirv and sil2100 ... (but sil is at the dentist)12:21
thostr_ogra_: thanks12:22
thostr_Mirv: can you reconfigure silo 1812:22
seb128thostr_, what did you change? did you add new components? if it's only mps from the same projects any lander can reconfigure12:23
thostr_seb128: we added a new component in order to get it finally compiling12:24
seb128k, I was just mentioning it in case12:25
seb128you need Mirv then I guess12:25
thostr_seb128: yep, trying... :)12:25
t1mpMirv: if I add the qt53 ppa on my desktop, will that also break the compiler?12:27
rsalvetiWellark: updated https://code.launchpad.net/~rsalveti/indicator-network/change-signal-strength-thresholds-android/+merge/223344, can you please check that again12:32
rsalveti?12:32
rsalvetiand bug 1329945 as well12:32
ubot5bug 1329945 in indicator-network (Ubuntu) "WWAN signal strength is reported lower than android in same location" [High,Confirmed] https://launchpad.net/bugs/132994512:32
rsalvetias I said, we can't simply change ofono to behave as you expected12:32
=== alan_g|lunch is now known as alan_g
=== boiko_ is now known as boiko
asacrsalveti: can you help thostr_ reconfigure a package in a silo?12:53
Mirvt1mp: I don't think the gcc-4.9 affects anything else than eg. platform-cpp that's being used on the phone and specifically uses gcc 4.9 (4.8 is still the default)12:56
rsalvetisure, that is the issue?12:56
rsalveti/usr/lib/gcc/arm-linux-gnueabihf/4.8/../../../arm-linux-gnueabihf/libdbus-cpp.so: undefined reference to `std::__once_call@GLIBCXX_3.4.11'12:56
rsalveti/usr/lib/gcc/arm-linux-gnueabihf/4.8/../../../arm-linux-gnueabihf/libdbus-cpp.so: undefined reference to `std::__once_callable@GLIBCXX_3.4.11'12:56
rsalvetiyay \o/12:56
rsalvetiwhen rebuilding indicator-network12:57
asacthostr_: ^^12:58
asacthostr_: what is the issue? rsalveti might be able to help12:58
asac14:21 < thostr_> Mirv: can you reconfigure silo 1812:58
asacrsalveti: Mirv: ^12:58
thostr_rsalveti: that's the same issue we see also for scopes12:58
rsalveticrap12:58
rsalvetiseems tvoss is not around12:59
thostr_rsalveti: tvoss might have a solution: https://code.launchpad.net/~thomas-voss/process-cpp/bump-so-name-and-major-version/+merge/22339012:59
thostr_but in order to test this I need somebody to reconfigure my silo12:59
rsalvetioh, this is painful13:00
ogra_rsalveti, known, libstdc++6 is broken13:00
ogra_doko is working on it afaik13:00
rsalvetibumping process-cpp is a pita13:00
rsalvetialright13:00
ogra_see backlog in #ubuntu-devel13:00
ogra_ate some peoples monrings already :)13:00
rsalvetiright, seems to be in progress13:01
rsalvetiwill come back to this later then :P13:01
ogra_heh, yeah, we can largely stop all builds13:01
ogra_and wait for the fix ...13:01
* ogra_ knows why he perfers packages full of shell scripts :P 13:02
ogra_(instead of C++ code)13:02
Mirvthostr_: done.13:09
thostr_Mirv: thanks13:09
Mirvit seems I skipped to timp's hilight earlier, sorry13:09
Mirvit looks like we'd have unity8/Qt crasher fixed now in 5.313:11
dobeyhmm13:11
dobeyi don't think a reconfigure will fix it...13:11
Mirvpopey: davmor2: if you have time, your ability to crash Unity 8 would be needed with the Qt 5.3 PPA - it seems to be Unity 8 crasher would be now fixed with Albert's fix that landed. note that you need unpack + dpkg -i *.deb the tarball from http://people.canonical.com/~tjyrinki/gcc/fix_gcc.tar to overcome the gcc-4.9 breakage in archives if you dist-upgrade13:16
Mirvit's the bug #132848513:16
ubot5bug 1328485 in unity8 (Ubuntu) "unity8 crashed with SIGABRT on Qt 5.3" [High,In progress] https://launchpad.net/bugs/132848513:16
t1mpI think I ran into a new bug in Qt 5.3 https://bugs.launchpad.net/qtubuntu/+bug/133097713:18
ubot5Ubuntu bug 1330977 in qtubuntu "2-finger scrolling with touch pad does not work in qt apps on Qt5.3" [Undecided,New]13:18
Mirvworks fine here though :P but running Ubuntu in VM like in there might cause some difference13:28
t1mpnote that in general (non-qt apps), mousewheel/2-finger scroll works fine13:28
Mirvso indeed I guess what'd be needed is Macbook user on native Ubuntu that'd test if there's a difference, or if it only happens in VM13:31
kgunnsil2100 Mirv ...so long story short, mir ftbfs last night for armhf, it was gcc4.9 bug fix stuck in proposed, so silo 16 got built against proposed...so it build but doesn't seem to boot...so i'm thinking13:35
kgunnsilo 16 might need to get rebuilt again, but no against proposed...13:36
kgunnthots?13:36
kgunnah...might be related to https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1328485/comments/1213:37
ubot5Ubuntu bug 1328485 in unity8 (Ubuntu) "unity8 crashed with SIGABRT on Qt 5.3" [High,In progress]13:37
dobeythostr_, Mirv: i'm confused. why is process-cpp in silo 18?13:38
Mirvkgunn: yeah the gcc-4.9 is now in too, so no help in there13:38
kgunnMirv: how do i see whether or not a silo will build against proposed or not ?13:39
Mirvdobey: I don't know myself why it was added specifically to that silo13:39
Mirvkgunn: I don't know, but from previous build logs like https://launchpadlibrarian.net/177743823/buildlog_ubuntu-utopic-armhf.mir_0.3.0%2B14.10.20140616.5-0ubuntu1_UPLOADING.txt.gz you can see that -proposed is in there.13:40
thostr_Mirv: it was added in an attempt to get it building13:40
thostr_dobey: ^13:41
dobeythostr_: unity-scope-click doesn't use process-cpp. the issue there is libunity-scopes-api. but i don't know if we should be rebuilding all the cpp libs in the silos just to try and get things building with the new libstdc++13:42
sil2100I hate dentists13:45
dobeysil2100: surely better than abi breakage in c++ compilers though13:45
sil2100...true13:45
sil2100;)13:45
Mirvpopey: davmor2: installing the mediascanner2 enabled music-app with pkcon install-local got me a working music app on Qt 5.313:47
popeyMirv: same here ☻13:47
Mirvyeah it seems pretty good, even if it has some known limitations at the moment13:47
davmor2Mirv: popey: \o/ nice to see that one line fix land ;)13:47
popeyhah13:48
Mirvremaining Qt 5.3 blockers would be the UITK toolbar bug, and oSoMoN/chrisccoulson's Oxide landing (could we maybe have a pre-release to build against Qt 5.3 already?), and... hey, that was it?13:48
dobeythis reminds me of that time when everyone in open source avoided c++ because gcc kept breaking abi13:48
davmor2popey: so is that going to land properly?13:48
popeyyeah, once tests pass13:48
* popey pokes balloons 13:48
davmor2popey: don't do that you might burst him13:49
Mirvand a third blocker whatever is needed from lool/pmcgowan regarding frameworks13:49
dobeypopey: don't do that! the balloons will pop13:50
Mirvbut we now have the SDK, Unity 8 crashes seem gone, music-app with that ^ .click package works. pretty awesome for today's fixes!13:50
Mirvoh and fourth blocker... rsalveti, are the -gles packages actually strictly speaking needed at the day of Qt 5.3 landing?13:51
rsalvetiMirv: yes13:51
rsalvetican try to get to that later today13:51
rsalvetiis that the only blocker now?13:51
rsalvetiMirv: emulator is critical now, we can't regress it13:52
mandelsil2100, hello, can ou take a look at https://code.launchpad.net/~mandel/ubuntu-download-manager/leak-symbols/+merge/22247213:53
Mirvrsalveti: ok. when do you think you could look at the issue I emailed you about?13:53
sil2100mandel: hey! Let me take a look in a moment :)13:53
Mirvok :)13:53
mandelsil2100, awesome, thx13:53
Mirvrsalveti: yeah I was mainly thinking if the emulator images are sort of snapshots that don't break at the moment something is upgrade, or if it needs to be always simultaneous13:53
Mirvrsalveti: but yes certainly we can't regress it13:53
Mirvrsalveti: I think the qtbase-gles in the PPA is properly synced, and if one could install the end result probably the other 6 package rebuilds wouldn't pose a problem. I also updated the qtdeclarative-gles there too but obviously it couldn't be built.13:53
Mirvqt3d, qtubuntu, ubuntu-ui-toolkit are just no-change rebuilds and qtmultimedia + qtlocation probably don't have much changes to think about13:54
rsalvetiright, we just need to get base done correctly indeed13:54
rsalvetiwill try to get to it later today13:54
Mirvthanks13:55
t1mpMirv: the no-scrolling in qt53 is quite annoying for me ;)13:58
t1mpMirv: fyi, https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/fixEmptyToolbarQt5313:58
Mirvt1mp: use Ubuntu compatible hw :) but seriously, it's weird though what could be changing to make it incompatible inside VM or something like that, but of course the event handling does often see changes. but also weird that zsombor had the same problem on trusty / 5.2 too14:00
Mirvt1mp: awesome. did you check all of gallery + notes + dropping letters yet?14:00
t1mpMirv: uhm. I fixed the non-visible toolbar items in notes-app.. but the UITK test still fails :s14:00
Mirvt1mp: hehe. better have gallery and dropping letters handy too if it seems tricky / volatile14:01
t1mpMirv: no, I understood that zsombi did NOT have problems with either trusty or utopic with 5.2. Only with 5.3 he had problems14:01
t1mpzsombi: ^ right?14:01
Mirvt1mp: he said "< zsombi> Mirv: mine one never worked with mouse wheel"14:02
t1mpMirv: mine == qtc with qt5.314:02
Mirvt1mp: nope, he was using trusty (no 5.3 there), but then reported that 5.2 on utopic (different VM?) worked14:03
t1mplets wait for zsombi to clarify14:03
alan_gcihelp: can you see what's different about the mako CI environment today? Mir is having a hard time that doesn't appear to relate to the MPs being built: https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/14:03
zsombit1mp: like what?14:03
t1mpzsombi: did your mousewheel work in trusty and in utopic with qt5.2? And did it break with qt5.3?14:04
zsombit1mp: mouse wheel scrolling with QtC or UITK gallery doesn't work with Qt5.314:04
t1mpzsombi: and with qt 5.2?14:04
zsombit1mp: it works like charm14:04
t1mpzsombi: ok, thanks for clarifying :)14:05
t1mpMirv: ^ works fine with 5.214:05
Mirvzsombi: and that's also on macbook with Ubuntu in VM? and it works also in 5.2+trusty, not just 5.2+utopic?14:05
zsombiMirv: yes14:05
t1mpMirv: I can also confirm that 5.2+trusty works fine inside the same vm14:06
Mirvok, I'm adding the tag back and changing the subject a bit. thanks.14:06
Ursinhaalan_g: hi, I'll have a look14:06
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #84 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
stgraberasac: I'm around now, what silo needs reconfiguring?14:10
sil2100kgunn: regarding landing line 9...14:15
kgunnyes?14:16
sil2100kgunn: I see it will lock many components, some of which are already allocated - you want an override for that? What is the ETA for this to land?14:16
kgunnAlbertA: ^14:17
kgunnsil2100 so we're ready now...but if we need to wait we will14:17
kgunnsil2100 so to answer more clearly, yeah, we wanna lock...14:18
kgunnif already locked projects, we'll need to wait14:18
=== Ursinha is now known as Ursinha-afk
sil2100kgunn: ok then, let's at least wait for one unity8 related silo to land14:23
=== alan_g is now known as alan_g|tea
sil2100mandel: so far looking at the symbols and the maps it looks really nice! This is why I like export maps, as then we only have the right symbols in symbols files in overall14:28
mandelsil2100, indeed, that was a great tip! I'll be using them from now on14:28
sil2100mandel: even though CI liked the merge, I'll just do a quick test build locally to test something and approve :)14:29
dobeyexport maps can be a huge pain though, with cmake14:29
mandelsil2100, sure, better safe than sorry14:29
mandeldobey, I did not have that many problems with them14:29
mandeland cmake :)14:29
elopiosil2100: this page has no instructions to test the mediaplayer14:29
elopiohttps://wiki.ubuntu.com/Touch/Testing14:29
sil2100Oh, hm14:30
=== Ursinha-afk is now known as Ursinha
sil2100elopio: the wiki doesn't want to load for me right now...14:33
dobeymandel: if you only have one .so, or all your .so builds  that link to the first .so have all required symbols under the same namespace, it's easy. but if you have a library and plug-ins for qml or other things that link to your .so, it can be a pain :)14:33
elopiosil2100: I can update it. But I would like to put the same command that jenkins uses, and I'm not sure which one is it.14:34
asacstgraber: think that is solved now :)14:34
asacstgraber: in general wonder if you know enough to help out on such things if sil is at lunch etc.14:34
=== alan_g|tea is now known as alan_g
asacthostr_: your silo reconfigure was solved, right?14:34
mandeldobey, I do have several .so and a qml plugin but the plugin is no allowed to use anything internal so it should throw errors if it uses private symbols, but I get the point, there are some of them I would have liked to hide even more14:35
thostr_asac: yes... however, we don't get anything build14:35
sil2100thostr_: what's wrong? Toolchain issues, or some other problems?14:36
thostr_yes, still gcc 4.8/4.9 issues14:36
stgraberasac: I can assign silos, reconfig, land, ... so long as Jenkins let me anyway (had some permission problems last week, hopefully it's all fixed now). Though I'm on US eastern so I doubt I'll be very helpful for when sil2100 is at lunch since I'll likely still be sleeping at that time :)14:36
sil2100I see that doko has a new gcc prepared in his PPA14:36
dobeymandel: yeah, the problem is that when you add the export map arguments to the target in cmake, cmake adds those export maps to any other targets that link to that target as well14:37
sil2100stgraber, asac: I guess normally when I'm having lunch Mirv is still around as support - this time the dentist was a bit unfortunate, as I'm not the one controllin the date and time for that one14:37
mandeldobey, really, even when you use set_target_properties?14:37
dobeymandel: i think so14:39
sil2100dobey: now that is something I didn't know, huh... well, never had problems with this as I only used those for simpler projects14:39
sil2100Where there was either one .so or 2-3 independent ones14:39
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | CI Train Status: #84 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
mandeldobey, , I've use nm a does not show other symbols, but I might just have been lucky14:40
dobeysil2100, mandel: i had problems with this when adding export maps to ubuntuone-credentials14:40
dobeymandel: well, the export map doesn't add symbosls that shouldn't be there14:40
dobeymandel: but it can block symbols from showing up, that should be there, in some cases :)14:41
mandeldobey, yes, but I have done nm on a target that was linked a diff one and saw no issues in udm14:41
dobeymandel: nm won't show you a list of symbols that you should have exported, but didn't. :)14:42
mandeldobey, I know, but I do look at the ones I'm expecting and all of them are there14:42
mandelagain, might be luck14:42
dobeymandel: well, independent libs are independent. so there are a lot of things that can affect (or not affect) how it works14:44
dobeythostr_: i think we just need to wait for doko to get the libstdc++ issue fixed in the archive, then rebuild the silos14:45
thostr_dobey: yes14:45
dobeyis there a silo that has something which actually uses process-cpp, in it?14:46
asacsil2100: dont worry. just trying to figure how more can help out :)14:46
asacthink we have a gap in EU timezone still14:46
kgunnthostr_: just catching up on backlog a little...you able to build? or just not boot ?14:55
kgunni was unable to build, but then they retargeted my silo to build against proposed...which built, but i can't seem to boot...and i suspect its related to this gcc churn still14:56
kgunnjust wondering as a data point to support or deny my theory14:56
loolMirv: hey, I'd like to add -dev2 frameworks in whatever silo the qt 5.3 landing gets; which one would that be?14:58
looldont think touch-meta is CI-ed though14:58
thostr_kgunn: yes, both has issues15:01
dednickfginther: just taking a look at some unity-system-compositor/devel & platform-api/devel CI jobs, and they dont seem to be using the mir staging ppa (from devel) for building.15:07
dednickfginther: unity-mir/devel is doing it correctly. This someone added D09add_ppa~mir-team~staging hook into job params.15:08
dednicks/this/think15:08
fgintherdednick, one moment15:10
* elopio stands on the vanguard line.15:12
elopiofginther: the messaging app jobs fail to install ofono. Could be a chroot problem.15:13
fgintherdednick, I can get that added shortly15:16
dednickfginther: thanks!15:16
fgintherelopio, I'm assuming this isn't normal:15:20
fginther/var/log/upstart/otto-setup.log: Setting up ofono (1.12.bzr6868+14.10.20140513.1-0ubuntu2) ...15:20
fginther/var/log/upstart/otto-setup.log: invoke-rc.d: unknown initscript, /etc/init.d/ofono not found.15:20
fginther/var/log/upstart/otto-setup.log: dpkg: error processing package ofono (--configure):15:20
fginther/var/log/upstart/otto-setup.log:  subprocess installed post-installation script returned error exit status 10015:20
dobeythostr_, asac: can we move process-cpp out of silo 018? unity-scope-click doesn't use it, and I don't want the process-cpp change to require gcc-4.9 to be blocked on libstdc++ abi compat issue being fixed or all the libs being rebuilt, when unity-scope-click doesn't use the library15:21
elopiofginther: yes, that's the problem.15:21
elopioI have the same version working without problems on my machine.15:21
elopioand the tests pass on mako. The error is only on trusty.15:21
elopios/trusty/utopic15:21
elopioon the jenkins' utopic.15:22
thostr_dobey: removed.15:25
thostr_sil2100: can you reconfigure silo 1815:25
sil2100thostr_: sure15:26
dobeythanks15:26
sil2100thostr_: done15:27
thostr_sil2100: thanks15:27
=== Laney is now known as mrage
=== mrage is now known as Laney
fgintheralan_g, I compared the package list from the passing run to the failing run, about the only difference is a new gcc 4.9.0-6ubuntu1 -> 4.9.0-7ubuntu115:32
fgintheralan_g, at least that's what is different in the mako image15:32
fgintheralan_g, all 4 of the test failures appear to be the same segmentation fault in mir_performance_tests15:33
alan_gfginther: thanks.15:33
fgintherdednick, unity-system-compositor/devel & platform-api/devel CI jobs are updated now15:42
dednickfginther: thanks15:43
fgintherdednick, will also make sure the others are updated while I'm at it15:43
=== gatox is now known as gatox_lunch
alan_gkgunn: ^^15:44
* ogra_ will be a moment late to the meeting (finishing dinner)15:58
sil2100ogra_: ok15:58
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #84 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
fgintherelopio, I have no idea yet why ofono is failing to install. I tried some live debugging on one of the otto nodes, but it installed cleanly. I'll take a closer look at what it's doing after lunch16:14
thostr_asac: ogra_: sil2100: doko says the package is about to be published. could you ping us (or everybody) once it is actually published so that we can start trigger builds16:19
ogra_its in afaik16:19
ogra_and the silos build against proposed anyway16:19
ogra_so you should be good16:19
thostr_ogra_: ok16:19
elopiofginther: thanks. sergiusens also said that it could be systemd. And awe was the last to touch the package, so they might be able to help you.16:19
popeywhat is /system/bin/sensors.qcom ?16:26
popeythats taking 10% of my cpu after the reboot16:27
popeyas is messaging app16:27
ogra_ricmm, ^^^^16:27
popeynowhere near as bad as it was, but still16:27
popeyhttp://paste.ubuntu.com/7659216/16:27
popeythats with the screen off16:28
popeyshouldn't these apps be paused ?16:28
ogra_"these apps" ?16:28
popeymessaging, apps which I started16:28
ogra_i only see messaging-app16:28
popeyright, previously it was addressbook, this time it is messaging16:29
ogra_yes, it should be sigstopped after a while16:29
popeyoh, its a deb, these aren't constrained are they?16:29
ricmmpopey: is that withthescreenlocked?16:29
ricmmarghh this keyb16:30
popeyyes16:30
imgbot=== trainguard: IMAGE 86 building (started: 20140617 16:30) ===16:30
ricmmpopey: does it go to sleep when dismissing to the right?16:30
popeyuh, i have no apps foregrounded16:31
popeyI'm sat at the app scope16:31
popeyand address-book is eating 40% now16:31
popeysil2100: ^16:31
ricmmso address-book does the 40% every now and then16:31
ricmmrenato can tell you more about that one16:31
ricmmbut it not sleeping is a whole different issue16:31
popeydefine "every now and then"16:31
ricmmcan you test other apps?16:31
ricmmdismiss and so on16:31
popeydefine "dismiss"16:31
popeyclose in app scope?16:32
ricmmswipe back to shell16:32
popeyright16:32
ricmmso send to bg16:32
popeyk16:32
popeywhatever app I open, and swipe away, if I get back to app scope, address-book is always eating 40%#16:32
ogra_=== Image #85 Promoted ===16:32
ogra_:)16:33
popeyswine ☻16:33
sergiusenspopey: close the camera app and see if the sensor cpu consumption lowers16:33
ricmmso my question is if the *other* apps you open, get suspended16:33
ricmmonce you go back to the dash16:33
ogra_heh16:33
ricmmthey should be suspended 3 seconds after you show the dash16:33
popeyyes16:33
ricmmok, so just address book16:33
popeyaddres-book does too sometimes16:33
ricmmsometimes? wth16:33
ricmmso wait out a full 4 seconds before checking if its suspended16:34
ricmmwhen you swipe to dash16:34
popeyits all good now16:34
popeybut earlier, it was eating 40%16:34
popeyand I had that after reboot, then re-open those apps16:34
ricmmright, about that, I remember renato saying something about it in malta16:34
popeysergiusens: i dont have camera open16:34
ricmmbut I dont know details, sorry16:34
popeyok16:35
davmor2popey: so for me I've just done a reboot syncevo- .... was using 93% for 3-5 seconds and now is fine.  highest cpu usage now is top at 2.)%16:35
ricmmthe 10% CPU in sensors.qcom and *-app is a known issue16:35
davmor22.0% even16:35
popeyok16:35
ricmmand will be solved with my soon-to-land orientation work16:35
popeythanks ricmm16:35
ricmmor re-orientation16:35
popeyif it's all known then good good16:35
popeyrenato: got a bug for the 40% address book cpu eating?16:36
renatopopey, ricmm, yes I saw that once, but I was unable to figure out what was happening16:36
renatopopey, are you able to reproduce it?16:36
popeyI have had it twice in the last hour16:36
popeyi have 350 contacts if that makes any difference16:36
popeyand two google accounts setup to sync16:37
renatopopey, I do not think so I am testing with 1500 contacts :D16:37
popeyget you mister friends!16:37
davmor2popey: and I thought you had too many ;)16:38
robruseb128, you got silo 1216:39
=== gatox_lunch is now known as gatox
popeyrenato: filed a bug for it bug 133107816:44
ubot5bug 1331078 in address-book-app (Ubuntu) "address-book-app consumes 40% sometimes when backgrounded" [Undecided,New] https://launchpad.net/bugs/133107816:44
renatopopey, thanks16:44
popeynp16:44
dobeywheeeeeee :(16:45
dobeyso new binutils didn't quite fix things, eh?16:51
davmor2popey: yay 6 reboots and now I see it but only when the addressbook is in the foreground the minute I switch to another app or close the addressbook it goes down to 016:52
t1mpMirv: would you like to review this? https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/fixEmptyToolbarQt53/+merge/22341216:53
t1mpMirv: did you notice an invisible header in galler-app with qt 5.3? I don't know if that bug exists with qt 5.216:54
davmor2popey: 4196 phablet   20   0  260964  61376  32380 T  0.0  3.3   0:53.33 address-boo+16:54
davmor2in foreground  4196 phablet   20   0  260964  61376  32380 S 45.5  3.3   0:55.98 address-boo+16:55
popeydavmor2: tap power rather than swipe the app away16:55
davmor2popey: slowly drops to 0.0 again16:56
* dobey wonders what to do about gcc 4.9 breakage16:57
davmor2dobey: it's been fixed apparently unless there is another breakage16:58
dobeydavmor2: it's still broken on arm afaict. the missing symbols in libfoo issues are gone now, but the previous issue of missing symbols in the thing being built, is back16:59
dobeyhttps://launchpadlibrarian.net/177798305/buildlog_ubuntu-utopic-armhf.unity-scope-click_0.1%2B14.10.20140617.5-0ubuntu1_FAILEDTOBUILD.txt.gz16:59
dobeyaka, back to where we started :-/16:59
ogra_dobey, that must be on your side, doko reverted everything16:59
Laneynein17:00
Laneyhttps://bugs.launchpad.net/ubuntu/+source/gcc-4.9/+bug/1329089/comments/917:00
dobeyogra_: reverted? he uploaded a new snapshot of binutils is all17:00
ubot5Ubuntu bug 1329089 in dbus-cpp (Ubuntu) "g++-4.9 binary incompatibilties with libraries built with g++-4.8" [Critical,In progress]17:00
Laneysomeone retried evo though, so watch if that works17:00
Laneyhttps://launchpad.net/ubuntu/+source/evolution/3.12.2-1ubuntu1/+build/610575317:00
ogra_dobey, he uploaded a complete revert in that new revision17:00
dobeyogra_: that's not what the diff says17:01
ogra_gcc-4.9 (4.9.0-7ubuntu2) utopic; urgency=medium17:02
ogra_  * Revert the fix for libstdc++/60326, introducing PR libstdc++/61532.17:02
ogra_thats what the changelog says here17:02
dobeyogra_: oh, i was looking at binutils17:02
ogra_dobey, which PPA/silo is that ?17:03
dobeyogra_: 01817:03
=== alan_g is now known as alan_g|EOD
dobeyit's only failing on arm17:03
ogra_says published  34 mins ago ...17:03
ogra_you might have just had an unlucky timing17:04
dobeythe build log has the 4.9.0-7ubuntu2 version of libstdc++617:04
dobeyso that reversion is there17:04
ogra_hmm, then i dont know17:04
dobeybut it's the same compilation issue on arm that we started with in the ppa yesterday17:04
ogra_slangasek, ^^^^ any idea ? that should build now as i understand it17:05
dobeythe MP that's being merged in that silo built fine on arm in jenkins17:06
slangasekogra_: olli_ has escalated this silo 018 failure to me17:06
ogra_ah, k17:06
slangasekthis is a different failure than the one before, and resembles the earlier failures from gcc-4.9 4.9.0-6ubuntu117:06
dobeylooks like jenkins already has a libstdc++6 and -dev package installed before it starts the build though, so i can't tell what it has17:06
dobeyright17:06
slangasekunity-scope-click seems to have also changed in the silo; so I'm test-building the new version with the previous libstdc++17:08
dobeyslangasek: yeah, there is a change that introduces usage of std::unordered_set, which i suspect is the root of why this is happening there17:08
dobeyi don't understand what gcc would be doing different on arm for that though17:10
ogra_sil2100, no mail today ?17:36
sil2100ogra_: writing it now, got preempted ;)17:36
ogra_:)17:36
sil2100My scheduler is sometimes really aggressive17:36
ogra_mine is only surprising :)17:37
ogra_(when unexpected meetings pop up and the like)17:37
imgbot=== trainguard: IMAGE 86 DONE (finished: 20140617 17:45) ===17:45
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/86.changes ===17:45
slangasekdobey: building current unity-scope-click with previous libstdc++6 does not hit this error (it hits the previous error of std::__once_callable).  So the latest regression seems to again be on the gcc side, not on the unity-scopes-click side.17:45
slangasekalthough, I do notice now that the actual failing reference (from the original failure) is from /usr/lib/arm-linux-gnueabihf/libunity-scopes.so, not from anything in the tree; perhaps libunity-scopes needs a rebuild17:46
slangasek(independent of the latest gcc problem)17:46
dobeyslangasek: original failure? i didn't see libunity-scopes in the original failure (this is the same failure as original, that i'm seeing now)17:47
slangasekdobey: sorry, by "original" I mean the one with gcc 4.9.0-7ubuntu117:47
dobeythe libunity-scopes missing symbols failure occurred prior to doko's latest reversion17:47
dobeyslangasek: one sec, let me look at the gcc upload history17:48
dobeyslangasek: ok, so the issue with -7ubuntu1 could possibly be fixed by rebuilding libunity-scopes-api and everything it in turn also depends on (rebuilding it alone i expect might fail with similar errors to what we got with it)17:50
slangasekmaybe17:50
slangaseklooking into it now17:50
dobeyslangasek: but that won't fix the issue now with -7ubuntu2 i don't think17:51
slangasekcorrect17:51
slangasekbut if that means there are two issues, I want to make sure we've got a handle on how to fix both of them so we're not losing more time to this17:51
dobeyright17:51
dobeyi just don't want to also lose time rebuilding the world with 4.9, and then having this same issue still re-appear again afterword17:52
dobeyslangasek: thanks for looking into this. i wish i could be more help17:55
slangasekit's not your responsibility to deliver a working toolchain, it's ours ;-P17:55
dobeyslangasek: indeed. but i like to understand what's broken when it's affecting my code :)17:56
renatopopey, I have a branch to you to test: https://code.launchpad.net/~renatofilho/address-book-app/fix-1331078/+merge/22345817:57
sil2100ogra_: https://plus.google.com/109159869108744115904/posts/SJ69CfvNPyc17:58
Ursinha/ci/topic18:00
Ursinhaargh18:00
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #84 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
=== doanac changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: doanac | CI Train Status: #84 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: doanac | CI Train Status: #85 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
popeyrenato: will take a look a bit later.18:21
sil2100Ok, I guess it's time for me to EOD, see you guys tomorrow o/18:37
kgunnrobru: mind unpointing silo16 at proposed?18:55
kgunnseems i'm getting ftbfs there18:55
robrukgunn, silo 16 has proposed enabled18:56
robruoh "unpointing", thought you said "updating"18:56
kgunnrobru:  no worries...i should use better speech18:56
robrukgunn, ok, proposed disabled, give it a shot18:56
tedgWhat's the status of the gcc 4.9 transition?19:00
tedgSilo tomorrow or risk today? :-)19:00
robrutedg, kgunn seems to still be struggling19:08
tedgrobru, He's an aggie though. I mean real people :-)19:10
robruaggie?19:10
tedgTexas A&M graduate. A fair number of "blond jokes" in Texas are aggie jokes.19:10
robruheh19:10
robrutedg, so anyway, slangasek or dobey would be the best people ask about the gcc thing.19:11
tedgrobru, Example: Did you hear about the Aggie that moved to Louisiana? Raised the average IQ in both places.19:11
dobeys/or dobey//19:11
robruouch19:11
tedgrobru, Do know some examples of the failures. I'm seeing something on gcc4.8 that is weired with process-cpp. Not sure if it's migrated and seeing the reverse transition.19:13
robrutedg, got a log?19:14
tedgrobru, https://launchpad.net/~ted/+archive/ppa/+build/6106103/+files/buildlog_ubuntu-utopic-i386.pay-service_0.1%2B14.10.20140602-0ubuntu1_FAILEDTOBUILD.txt.gz19:14
slangasektedg: so far the issues we've been seeing have been link-time; I don't know anything about test suite failures19:15
tedgOkay, might be something else then.19:15
tedgJust kinda weird. Doesn't happen locally.19:15
slangasektedg: unless it's the case that this is one of the libraries that requires revdeps to be built with the matching compiler19:16
slangasekactually, process-cpp is listed on bug #132908919:16
ubot5bug 1329089 in dbus-cpp (Ubuntu) "g++-4.9 binary incompatibilties with libraries built with g++-4.8" [Critical,In progress] https://launchpad.net/bugs/132908919:16
slangasekbut tvoss marked it as not affected19:16
robrutedg, I dunno much about this C++ stuff. your thing is just a test failure though, kgunn was having some build failures before even testing19:16
slangasektedg: might be worth checking with tvoss; might also be worth checking if building pay-service with g++-4.8 instead of g++-4.9 makes a difference.19:17
slangasektedg: were you reproducing locally on i386 or amd64?19:17
slangasek(s/reproducing/failing to reproduce/)19:17
tedgslangasek, That seemed to be built with 4.8, not sure why that is, but I was curious if that was the issue.19:17
tedgPPA fails on both.19:17
slangasekok19:17
slangasekall of the fixes we've been slathering on gcc-4.9 have been link-time changes, so this is either bug #1329089 or an unknown issue19:18
ubot5bug 1329089 in dbus-cpp (Ubuntu) "g++-4.9 binary incompatibilties with libraries built with g++-4.8" [Critical,In progress] https://launchpad.net/bugs/132908919:18
slangasekah, but this build is with the current gcc-defaults, so you are using gcc-4.8 for the build anyway19:19
slangasekg++-4.8, even19:19
slangasekand process-cpp hasn't been rebuilt since May, so that's also unrelated here19:19
slangasektedg: so unless there's another library in your stack, other than process-cpp, affected by bug #1329089, it appears to be an unrelated issue19:20
ubot5bug 1329089 in dbus-cpp (Ubuntu) "g++-4.9 binary incompatibilties with libraries built with g++-4.8" [Critical,In progress] https://launchpad.net/bugs/132908919:20
tedgIt could be me just screwing up too :-)19:21
=== josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #85 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
slangasekwell, whatever it is, it doesn't look related to gcc-4.9 AFAICS19:24
slangasekthe sure way to rule that out, if you can reproduce it, is to try downgrading libstdc++6 to the trusty version and rerunning the test19:24
kgunnslangasek: uh....i'm getting FTBFS again...19:25
kgunn/usr/lib/gcc/arm-linux-gnueabihf/4.8/../../../arm-linux-gnueabihf/libmirserver.so: undefined reference to `std::__once_functor@GLIBCXX_3.4.11'19:25
kgunnsame 2 funcs tvoss was mentioning19:26
kgunnsorry meant to paste19:26
kgunnhttps://launchpadlibrarian.net/177815633/buildlog_ubuntu-utopic-armhf.unity-system-compositor_0.0.3%2B14.10.20140617.4-0ubuntu1_FAILEDTOBUILD.txt.gz19:26
dobeytedg: is there a single MP for that pay-service build? or is it a bunch of MPs?19:29
tedgdobey, I moved it into a single19:30
dobeytedg: what's the url for the MP?19:30
tedgdobey, It's a secret! :-)19:30
tedgdobey, https://code.launchpad.net/~indicator-applet-developers/pay-service/devel/+merge/22310619:30
dobeytedg: and what ppa was that build failure in?19:33
tedgdobey, Just mine.19:34
tedgVirtualized, nothing special, etc.19:34
dobeyoh it failed on amd64 too19:35
dobeyweird19:35
tedgYeah, trying trusty19:35
tedgJust to remove that variable.19:36
tedgIt's an odd failure though. And didn't happen on Jenkins.19:36
* tedg blames Launchpad ;-)19:36
dobeyyeah i think it's unrelated to the gcc 4.9 stuff19:37
dobeyon the other hand, you did change that code :)19:39
* tedg claims bzr blame is a liar19:40
slangasekkgunn: yes, __once_functor has gone away again between 4.9.0-7ubuntu1 and 4.9.0-7ubuntu2; it was not present in libstdc++6 from 4.8; we should try a no-change rebuild of libmirserver19:41
kgunnslangasek: that's exactly what i _think_ i had done, e.g. force rebuild/ignore19:42
slangasekthis doesn't help with the unity-scope-click failure, which is about __get_once_mutex() refs being generated by the headers; but a no-change rebuild of libmirserver should fix that unity-system-compositor build failure19:42
slangasekhmm19:42
slangasekwhich ppa is this in?19:42
slangasek01619:43
slangasekmir failed to build19:44
slangasekand unity-system-compositor needs mir rebuilt first19:44
kgunnslangasek: mir is listed first in the mp list...19:44
kgunnthis is how it always builds19:44
slangasekkgunn: sorry, not sure what you mean19:45
slangasekthe order of the mps in the landing does not enforce ordering of the builds19:45
slangasekyou would need versioned build-dependencies to do that19:45
kgunnslangasek: hmmm, not what didier said long ago...19:45
kgunnslangasek: my silos would fail constantly...unity-mir, usc, platform-api are all rdeps of mir19:45
kgunnso mir has to build first19:46
slangasekregardless, the mir it's building against was built against libstdc++6 4.9.0-7ubuntu1; we need it rebuilt (successfully) against libstdc++6 4.9.0-7ubuntu2 and u-s-c to be retried against it once built19:46
dobeywell, it doesn't matter which one builds first, if the builds are failing anyway19:46
slangasekwell, in this case all of these packages were being tried in parallel19:46
kgunnslangasek: and those rdeps are version dep'd on mir19:46
kgunnin fact that is the only change for those (e.g. mir >= 0.3.0)19:47
slangasekbut there's already a mir >= 0.3.019:47
slangasekand it has the wrong abi and needs rebuilt19:47
kgunnslangasek: how so? i'm doing force-rebuild...it should be blown away19:47
dobeykgunn, slangasek: mir failed to build on arm in that silo, for similar reasons as to why unity-scope-click is failing, afaict19:47
slangasekevidently it's still in the ppa?19:47
kgunnif it doesn't blow away the new version of mir in the ppa then that _is_ a bug19:48
kgunnrobru: ^19:48
dobey/usr/include/c++/4.8/mutex:779: undefined reference to `std::__get_once_mutex()'19:48
kgunnwouldn't you agree19:48
slangasekanyway, root cause - mir ftbfs,19:48
slangasek/usr/include/c++/4.8/mutex:779: undefined reference to `std::__get_once_mutex()'19:48
kgunnslangasek: agreed19:48
tedgI think that's a "fix with CI Airline" bug.19:48
robrurobru, what's going on? build is failing because of previous silo contents?19:48
kgunntedg: thanks ted :P19:48
kgunnrobru: not necessarily19:48
slangasekrobru: that appears to be the implication; kgunn wanted u-s-c in https://launchpad.net/~ci-train-ppa-service/+archive/landing-016/+packages built against the mir there, but mir ftbfs on armhf and u-s-c was still tried19:49
tedgkgunn, No, seriously. I think it's the same thing that bit ricmm with the platform API versioning.19:49
robrukgunn, you're right that CI Train is sloppy about previous silo contents. if necessary I can move you to a different one19:49
kgunnrobru: let's do that19:49
slangasekrobru: all that would do is make the package dep-wait19:49
robruslangasek, right, as infinity advised, but then we can retry the build19:50
robruright?19:50
slangasekthere's no build for you to retry19:50
slangasekneed to sort out the toolchain breakage under mir19:50
robruslangasek, well, after I upload to a new silo there would be19:50
slangasekno, retrying the build would be a waste of time19:50
robruslangasek, ok, let me know what I can do to help ;-)19:50
slangasekrobru: you could remove the old mir binary packages from the silo, if you want? :)19:51
slangasekthen when we get this fixed it should retry automatically19:51
robruslangasek, just mir or blow away the whole silo?19:51
slangasekrobru: just the /old/ mir binaries19:51
slangasekno need to take out the successfully-built amd64/i386 binaries from the current source19:51
slangasek->lunch19:52
kgunnthis seems not copacetic19:52
kgunnthen you've got sort of mish-mash of built-against-archive per archs....19:52
* dobey notes we have too many things that get abbreviated as u-s-c19:53
robruslangasek, kgunn ok well I've deleted all the superseded binaries19:53
kgunnrobru: ack19:54
* kgunn goes to look at ppa19:54
robrukgunn, it'll probably look mostly the same since the newest-built binaries are still there19:54
kgunnand btw, tedg...yeah you're right19:54
kgunnrobru: curious...is there a way to target just armhf ?19:55
robrukgunn, not that I know of... not in a ppa anyway. locally crossbuilding is a thing19:55
* tedg assumes that kgunn means he was right about the aggie jokes19:56
kgunnstop it tedg19:56
kgunn:)19:56
kgunndobey just a double check, so https://code.launchpad.net/~thomas-voss/process-cpp/bump-so-name-and-major-version didn't help you ?20:02
dobeykgunn: no, unity-scope-click doesn't use process-cpp20:02
dobeyso rebuilding it with gcc 4.9 would be completely useless for us :)20:02
tedgUhg, fails on trusty too. So odd.20:08
dobeytedg: what commands are those tests running exactly?20:12
tedgdobey, brings up the dbus interfaces and throws a few messages at it. gdbus.20:13
dobeytedg: but what is the command process-cpp is running exactly? it could just be the commands are failing to start because of permissions restrictions on the launchpad builders, which don't exist in jenkins or locally20:16
robrudobey, mhr3: you guys want a reconfig on silo 18? I see a new MP in there that wasn't part of the original build20:17
tedgdobey, It's running under dbus-test-runner, so that should be building the dbus session for the tests.20:17
dobeyrobru: what new mp?20:17
robrudobey, somebody added https://code.launchpad.net/~thomas-voss/process-cpp/bump-so-name-and-major-version/+merge/223390 into your unity-scope-click in silo 1820:18
dobeyrobru: no, that MP should not be in silo 1820:18
robrubut just in the spreadsheet, it hasn't been reconfigured or built yet20:18
dobeyrobru: it was reconfigured/built there earlier, but it is completely unrelated to unity-scope-click20:18
dobeyrobru: it should be removed from the silo config20:19
robrudobey, ok, not sure how that got there, but I pulled it out20:19
dobeyor i guess just from the spreadsheet if that's the only place it appears20:19
robruyeah20:19
robruunfortunately I have no way of knowing who put that in the spreadsheet there.20:20
dobeyrobru: there was some confusion about all the build failures this morning and thostr_ asked for it to be added to the silo. i later asked for it to be removed, as it's unrelated to the scope, and i didn't want the scope failing to block landing process-cpp if that change needs to land for other things20:21
robrudobey, ah ok20:21
kgunnrobru: hey mind punching reconfig on silo16 ? on tvoss' advice gonna give his mp a shot20:29
robrukgunn, alright20:30
robrukgunn, oh you need the MP URL, not the branch URL20:31
kgunndamn it...doh!20:31
kgunnrobru: ok...now20:32
robrukgunn, alright you are go for build20:33
dobeyslangasek: hey. just curious if you've been able to figure anything out yet with the once_mutex stuff21:22
kgunnrobru: well...that was interesting...fail, can you reconfig silo16 again ?21:26
robrukgunn, sure21:28
robrukgunn, done21:29
kgunnta21:30
oSoMoNrobru, hey, can we publish silo 7 ?21:35
robruoSoMoN, well, it's not marked testing pass. did you test it?21:36
robruactually not even built ...21:36
robruweird status21:36
oSoMoNrobru, yes, packages were copied from another PPA over to the silo21:36
oSoMoNrobru, and it’s been tested and acked by dbarth and myself21:37
robruoSoMoN, oh, I see, it's not an MP. I'll have to WATCH_ONLY build it before citrain will let me publish21:37
oSoMoNrobru, is that a trigger for the script that updates the status?21:37
robruoSoMoN, yeah, pretty much21:38
dobeykgunn: i don't think a reconfig is going to help mir build on arm though :)21:38
slangasekdobey: no progress yet; it was lunch then phonecall for me.  I'm going to braindump to a bug report ASAP21:39
dobeyslangasek: ok, thanks21:39
kgunndobey after a discussion with tvoss i add his process-cpp mp...i didn't have hope, but worth a shot, so reconfig was ridding the silo of that21:39
robruoSoMoN, ok, published21:40
oSoMoNrobru, awesome, thanks!21:40
robruoSoMoN, you're welcome!21:40
kgunndobey so i think we double-proved it didn't help21:40
dobeyah21:42
dobeykgunn: time to submit a paper to the New England Journal of WTF then, perhaps ;)21:42
kgunnlol21:43
kgunndobey yeah, i didn't really get why he even thot'd help...i mean, seems to me this is just mismatch symbols on libstd21:44
dobeyi'll just have to wait for foundations to fix it i guess21:45
oSoMoNrobru, what does "oxide-qt (1.0.2-0ubuntu2) is in no known space (and time)" mean?21:45
robruoSoMoN, means it hasn't been copied to proposed yet, should be there soon though21:45
oSoMoNah ok, it kinda sounded scary…21:46
dobeywhee, and now jenkins is starting to catch up with archive brokenness21:46
renatoelopio, ping22:22
robruboiko_, you got 1322:56
elopiorenato: pong22:58
renatoelopio, one of the tests was failing22:59
renatoelopio, I create a woraround22:59
renatoworkaround22:59
renatolet me send you the link22:59
renatohttp://bazaar.launchpad.net/~renatofilho/address-book-app/new-visual-contact-editor/revision/21022:59
renatoI think this is a bug on SDK,22:59
renatois very hard to scroll if you have fields on the flickable23:00
elopiorenato: I'm looking at the video of the error.23:03
elopioseems wrong indeed.23:03
renatoelopio, I was able to reproduce the problem on my desktop23:03
elopiorenato: so, sometimes, you swipe and nothing happens?23:03
renatoelopio, yes the field eats the events23:04
renatoif you have a field in the are where you click23:04
renatobut works in the second time23:05
elopiorenato: got it. Can you please report a bug and mention it on the workaround comment?23:06
renatook23:06
elopiorenato: and are you sure it will always work doing it twice?23:07
elopioif not, then maybe it would be a better idea to return to the tabs to focus while the bug is fixed.23:07
renatoelopio, there is a bug alredy: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/120502423:07
ubot5Ubuntu bug 1205024 in Ubuntu UI Toolkit "TextArea reacts to pressed and does not react to cancel events" [Undecided,New]23:07
renatoelopio, works for me :D, lets wait for jenkins23:10
boiko_robru: thanks23:11
robruboiko_, you're welcome23:11
elopiorenato: I confirmed the bug. I can see it happening here too.23:13
elopiofginther: late ping about the gatekeeper job. For when you have some time, I'll be here.23:17
=== boiko_ is now known as boiko

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