george_eI think I've figured out what's happening: http://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/launcher/XdndStartStopNotifierImp.cpp#L2800:07
george_eEvery time a window is mapped/unmapped, a timer is started that causes a signal to be emitted when the state of any of the mouse buttons changes.00:07
veebersdidrocks: ping06:19
didrockshey veebers06:19
veebersHi didrocks how's everything?06:19
veebersdidrocks: who can I annoy about this bug? https://bugs.launchpad.net/ubuntu/+source/ust/+bug/116335806:20
didrocksveebers: I'm good, thanks! yourself?06:20
ubot5Launchpad bug 1163358 in ust (Ubuntu) "Missing liblttng-ust-ctl.so.0" [Undecided,Fix released]06:20
didrocksveebers: it's fixed, isn't it?06:20
* didrocks looks06:20
veebersdidrocks: can't complain, days are getting colder and darker; but at least still some sun06:20
veebersdidrocks: I'm experiencing the same issue even with that version (have commented on that bug)06:20
didrocksveebers: the new soname is liblttng-ust-ctl.so.106:21
veebersdidrocks: hmm, but running the command lttng gives the error re: liblttng-ust-ctl.so.0: cannot open shared object file: No such file or directory06:22
veebersdoes that mean something is incorrect with lttng-tools?06:22
didrocksveebers: right, I think lttng-tools wasn't rebuilt against latest liblttng-ust06:22
didrocksveebers: I'm trying that, in a chroot06:23
veebersdidrocks: cool, thanks06:23
veebersdidrocks: Dinner is ready, I'll be back a little later on06:25
didrocksveebers: enjoy!06:26
didrocksveebers: hum, the -tools FTBFS06:26
didrocks/usr/bin/ld: tp.o: undefined reference to symbol 'rcu_dereference_sym'06:26
didrocks/usr/bin/ld: note: 'rcu_dereference_sym' is defined in DSO /usr/lib/liburcu-bp.so.1 so try adding it to the linker command line06:26
didrocks/usr/lib/liburcu-bp.so.1: could not read symbols: Invalid operation06:26
didrocksso I guess we can't just rebuild the old version06:26
mzanettigood morning07:20
veebersdidrocks: d'oh that sucks, how do we/I proceed from here?07:27
didrocksveebers: we are going to merge with debian, suck to do that that late though :/07:27
didrocksveebers: before PS is using any tool, it would be cool to ensure we can maintain it (or PS to maintain them themselves ;))07:28
veebersdidrocks: ah ok, thank you for taking care of that07:28
didrocksno worry!07:28
veebersdidrocks: what's a good way to ensure that we can maintain something? (i.e. from my point of view)07:29
didrocksveebers: ensure that we have a good "ack" from distro people, bringing that to ubuntu-devel ML07:30
didrocksveebers: as all the tools you are using, they should be maintained, so in main07:30
veebersdidrocks: mostly I just check is there a ubuntu package? yes awesome I'll use it (for personal projects etc.)07:30
didrocksand we need to figure out who will maintain them, and so on…07:30
didrocksveebers: check the package is in main07:30
veebersdidrocks: ack, thanks for the info. I'll share this sentiment with those involved too07:31
didrocksexcellent, thanks veebers ;)07:31
didrocksoh something else07:31
didrocksdo not relaunch the generic job alone07:32
didrocksthis won't fix the -check jobs that are monitoring it07:32
veebersdidrocks: ah ok07:32
didrocksso, only do it if you want to check that a UTAH fix fixes something07:32
veeberswhat's the prefered way of doing that (instead of just building and c&p-ing the parameters)07:32
didrocksveebers: do you know a little bit of daily release?07:32
veebersdidrocks: a little bit, not a massive amount07:33
didrocksveebers: maybe we should plan to have a hangout sometimes if you wish, I don't want to take too much of your time today :)07:33
veebersdidrocks: yeah sure sounds good, or failing that at the sprint07:33
didrocksveebers: yep, good as well :)07:33
didrocksveebers: just remind me about it please!07:34
veebersdidrocks: will do :-)07:34
didrocksthanks ;)07:34
seb128what happened to the hud in the indicators raring tests?07:53
seb128ups indicator->unity07:53
didrocksseb128: what job are you talking about?07:55
didrocksthis isn't the unity raring tests07:55
didrocksthis is the unity head tests07:55
seb128didrocks, shrug, I came from
didrocksyou don't see it complicated there07:56
didrocksso you don't have the run number07:56
didrocksit will be either 42 or 43 I guess07:56
seb128clicked on the blinking "ps-generic-autopilot-release-testing" line07:56
seb128I guess from the url I gave, I need to click on the #1607:57
seb128the console output07:57
seb128and use the links in there when they will be in it?07:57
didrocksbut this only appears once the job finishes07:58
seb128one day I will manage browsing jenkins and find me way ;-)07:58
didrocksnot sure if jibel knows if there is a way to know about this before ^07:58
didrocksseb128: heh :)07:58
didrocksbut I agree, it's a PITA07:58
didrocksand we need a dashboard to agregate that07:58
didrocks(but I don't know if we have enough "running now" infos)07:58
seb128ok, I guess unity is red because the previous run fail on a broken ati round?07:59
seb128intel/nvidia numbers seem fine08:00
didrocksseb128: yeah, yesterday's one08:00
didrocksseb128: it was published08:00
didrocksI asked mterry to do so08:00
didrockshey sil2100! how are you?08:01
sil2100didrocks: hello! Fine fine, fighting GIR a bit right now - what's up?08:01
seb128didrocks, sorry for the questions btw, trying to keep an eye on things daily and to get an hang of the details ;-)08:01
seb128sil2100, hey08:01
didrocksseb128: no worry ;)08:01
sil2100seb128: hello ;)08:01
didrocksseb128: TBH, I had a look myself before ;)08:01
didrockshence the quick answer :p08:01
tsdgeossil2100: that bug about the qt popups, should it be fixed in raring already?08:02
didrockssil2100: just wanted to know where you are at with indicator-messages, do you think we can have parallely installable by today or it will be need later on?08:02
sil2100didrocks: it should be ready today08:03
didrockssil2100: sweet! btw, can you update the spreadsheet once it's done with the criterias we have?08:03
sil2100didrocks: it's basically ready, just don't want to modify too much code to make GIR work parallely08:03
sil2100didrocks: ACK!08:03
didrockssil2100: thanks! :)08:04
sil2100tsdgeos: let me see - I think it got merged into trunk right now, but need to check if the raring branch got in08:04
jibeldidrocks, you cannot because the build and the workspace are created when the job starts, and since there is a single AP job for everything you'll have to wait.08:04
didrocksjibel: so, no way to know which run will have "this and this and this" parameters before it actually runs?08:04
didrocksor that the -check job will trigger run #42 of this job?08:05
didrocks(when it's waiting for job #41 to finish)08:05
sil2100tsdgeos: shit, it didn't have a commit message, so it didn't get merged08:06
tsdgeossil2100: ouch08:06
sil2100tsdgeos: re-approving08:06
jibeldidrocks, not before they start.08:07
didrocksjibel: so, jenkins just track that into memory for the jobs to run and no xmlrpc mechanism to query that?08:09
Saviqmzanetti, hyum, so the whitespace test already made that happen (the 100% coverage), right?08:13
seb128didrocks, what's the vcs for unity-lens-video ?08:17
seb128didrocks, control says lp:~unity-team/unity-lens-video/trunk but that doesn't exist08:17
didrocksVcs-Bzr should be set to the right one?08:18
* didrocks tries with a s08:18
seb128didrocks, I can't find it on https://code.launchpad.net/~unity-team08:18
didrocksunity-lens-video: from cupstream2distro-config08:19
didrockslet's see the latest build08:19
seb128didrocks, lp:unity-lens-video then?08:19
seb128that works08:19
seb128didrocks, if I MR against that, it will land in raring?08:20
mzanettiSaviq: dunno which ones exactly08:20
* didrocks blames again ken to have done something totally different for his scopes :/08:20
didrocksseb128: yep08:20
didrocksseb128: do you mind changing Vcs-Bzr as well?08:21
seb128didrocks, thanks, should I update the control Vcs-Bzr08:21
seb128will do ;-)08:21
didrocksseb128: I think something with bzr+ssh://bazaar.launchpad.net/+branch/unity-lens-video/ should work08:21
didrocksseb128: maybe trying with lp:unity-lens-video?08:21
didrocksso that we really target trunk08:21
didrockswhatever the name is08:21
seb128lp:unity-lens-video works08:21
mzanettiSaviq: but if a test opens every file, yes, that will cause that08:21
Saviqmzanetti, http://bazaar.launchpad.net/~unity-team/unity/phablet/revision/57508:21
didrocksseb128: oh lp: works in Vcs-Bzr? awesome :)08:22
Saviqwhy didn't we notice that before...08:22
didrocksseb128: we should go with this short form for everything :)08:22
tsdgeosmzanetti: you have whitespace, noOoOOoOOoOOoO08:22
seb128didrocks, ah, you meant for the Vcs-Bzr, sorry I though you were speaking about the target08:22
didrocksno, Vcs-Bzr…08:22
* tsdgeos finds it silly that we have to wait 1 hour to get notified we have whitespace and the MR won't pass CI08:22
mzanettiSaviq: yep. looks like it does08:22
tsdgeosdon't want to think how's this going to look like when we're pressed to do a release08:23
Saviqtsdgeos, you don't08:23
Saviqtsdgeos, you have local tests08:24
Saviqtsdgeos, that you should run before committing08:24
Saviqor at least before pushing08:24
tsdgeosSaviq: tell mzanetti ;-) he did the hook and not even he is running it :D08:24
mzanettitsdgeos: ?08:24
* mzanetti has nothing to do with the whitespace thingie08:25
Saviqmzanetti, he meant the on-commit test hook08:25
Saviqtsdgeos, make qmluitests is too long, but make test should be fine08:25
mzanettiyeah... the commit hook doesn't work out08:25
Saviqmzanetti, if we only run `make test`, that should be better08:26
tsdgeosmzanetti: https://code.launchpad.net/~mzanetti/unity/phablet-test-people-preview/+merge/158129 failed because of whitespace08:26
mzanettiSaviq: not really, its just too annoying if it kills the commit message you just wrote because you didn't build all the parts that are required to test something you haven't ever seen before08:26
Saviqmzanetti, use qcommit, it will not kill your commit message08:27
Saviqand doesn't QtCreator strip trailing wspaces by default?08:27
mzanettiSaviq: yes, it does08:27
Saviqbut yeah, regardless, we need to fix the QML coverage08:28
mzanettiSaviq: means disable it08:28
Saviqmzanetti, disable what?08:28
mzanettithe QML coverage08:28
Saviqmzanetti, no, fix it08:28
Saviqmzanetti, we don't need need no-qml unit tests on qmluitestrunner, do we?08:29
mzanettiSaviq: the only way I see is not to have any tests that open all files08:29
mzanetti(in the short term)08:29
mzanettiwe could define a new target tho08:30
Saviqmzanetti, yeah, that's what I'm thinking08:30
Saviqmzanetti, to not run the non-qml unittests on qmluitest jo08:30
mzanettilike "make whitespacetests" or the like08:31
mzanettithose could still be included in make alltests but not in the runtests.sh script08:31
Saviqmzanetti, I was thinking the other way round08:32
Saviqmzanetti, we only run qml tests on qmluitest job08:33
Saviqmzanetti, it doesn't collect c++ coverage from there, does it?08:33
mzanettiSaviq: it does08:33
mzanettiSaviq: and also the make check target has contains qml-only tests too08:33
Saviqmzanetti, that's fine08:33
Saviqmzanetti, but only runtests.sh monitors the files opened08:33
Saviqmzanetti, so we just need to make sure that runtests.sh only runs qml tests08:34
Saviqboth unit and UI08:34
Saviqand, btw, won't the "alltests" target cut it already?08:34
mzanetticut what?08:34
Saviqmzanetti, `make alltests` runs all the qml tests, doesn't it?08:35
Saviqmzanetti, but not the "usual" tests08:35
mzanettiSaviq: mall alltests run ALLtests08:35
mzanettiSaviq: make alltests run ALLtests08:35
jibeldidrocks, you can get these informations from the API for example http://paste.ubuntu.com/5697798/ but apart from the tooltip when you rollover the job on the build queue, I don't know where it is exposed on the UI.08:36
mzanettiSaviq: ok... so in the end we will have this:08:36
Saviqmzanetti, no it doesn't08:36
Saviqmzanetti, it's a custom target that we only add to via the add_qml_test macro08:36
didrocksjibel: ah, it's already a good news! so if we plan to do a dashboard, we can get those info :) Thanks for trying!08:37
Saviqmzanetti, if tests are only defined using add_test()08:37
mzanettitrue... you're right...08:37
Saviqmzanetti, they don't run on make alltests08:37
mzanettiSaviq: I'm starting to wonder if its a good idea that we have all this stuff in one and the same project08:37
Saviqmzanetti, so can we generate c++ coverage from `make test` and qml coverage from `make alltests`08:38
Saviqmzanetti, it's fine, we just have to cooperate08:38
Saviqmzanetti, and those kind of things would bite us one way or another08:39
nic-doffaySaviq, do you have a moment to discuss the tests I need to do for the infographics?08:39
Saviqnic-doffay, in 20 mins?08:40
nic-doffaySaviq, sure np.08:40
seb128didrocks, https://code.launchpad.net/~seb128/unity-lens-video/correct-search-hint-string/+merge/15829408:41
didrocksseb128: approved! thanks ;)08:42
seb128didrocks, thank you ;-)08:42
Saviqmzanetti, so, that should fix qml coverage: http://pastebin.ubuntu.com/5697811/08:43
Saviqmzanetti, and we only need to make sure that `make check` is run in the job, too, to generate c++ coverage08:43
Saviqmzanetti, is that not correct?08:44
mzanettiSaviq: yeah... but we should rename it to make qmltests and add another make alltests target to really execute alltests08:44
Saviqmzanetti, sure08:44
mzanettiSaviq: people are not going to type 5 make targets before committing... knowing myself I'm actually already worried about one :D08:45
Saviqmzanetti, I'm on it, can you take care of the job changes?08:45
mzanettiSaviq: are we going to remove the qml unittests from the make check target too then?08:46
Saviqmzanetti, do we need to? is it a problem that they run twice?08:46
Saviqmzanetti, I know it's time08:46
mzanettiSaviq: yeah... just thinking about time...08:46
mzanettiin that case we might merge unittests and qmluitests indeed08:47
mzanettiwell... lets see how it grows08:47
Saviqmzanetti, yeah, let's deal with it when it becomes a problem08:48
Saviqmzanetti, TBH I miss the ability in CMake to have multiple test targets08:48
mzanettiSaviq: +108:50
Saviqthat would save us some hacks08:50
mzanettiI'll poke alexander :D08:50
mzanettiSaviq: I *think* the job should be ok... I runs make check too08:55
mzanettiSaviq: I guess I should disable the license check in jenkins again then... no need to run it twice08:57
Saviqmzanetti, it's not merged yet, though08:57
mzanettiSaviq: ah no... there's still the issue with generated files08:57
Saviqmzanetti, just noticed something08:58
Saviqmzanetti, runtests doesn't take .js into account08:58
Saviqmzanetti, that on purpose?08:58
mzanettitrue... no... just forgot it08:58
mzanettishould do I'd say08:58
Saviqmzanetti, fixing08:59
didrocksjibel: I've added and deployed all future stacks we know as of now so that you can do the creation in batch: http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro-config/trunk/files/head:/stacks/head/09:00
jibeldidrocks, ack, appended to my todolist09:01
Saviqmzanetti, https://code.launchpad.net/~saviq/unity/phablet.fix-qml-coverage/+merge/15829809:02
mzanettiSaviq: why are we not allowed to do in-source builds any more?09:03
Saviqmzanetti, because they're evil09:03
didrocksjibel: thanks :)09:03
mzanettiSaviq: no, they're convenient09:03
mzanettiSaviq: I fully agree that out of source builds must work and are a good thing09:04
Saviqmzanetti, in-source builds hide issues09:04
mzanettiSaviq: but for just branching something, building running tests it just adds unneeded hazzle09:04
Saviqmzanetti, ./build builds out of source for you09:04
Saviqmzanetti, ./run runs out of source09:05
Saviqmzanetti, the only thing is that you need to `make -C builddir`, which is, I agree, not convenient09:05
Saviqmzanetti, and I'm thinking of "forwarding" make to builddir by default09:05
Saviqshould be doable by a simple static Makefile in top dir09:05
mzanettiSaviq:  ./build forces me to build all deps from scratch09:06
Saviqmzanetti, huh?09:06
Saviqmzanetti, how so?09:06
Saviqmzanetti, you just need a ../unity_build09:07
mzanettiSaviq: well, let me check better, just have ran it for the first time and it complains09:07
Saviqand whether you're using colocated branches (which I recommend)09:07
Saviqor just branches in dirs09:07
Saviqyou just need to make sure ../unity_build is there09:07
Saviqand not care about it unless something changes there09:08
Saviqmzanetti, out-of-source are just closer to what actually happens on the builders09:11
Saviqmzanetti, just one more way to let us fail faster09:11
mzanettiSaviq: sure. still its not always required and anforcing it wastes time09:11
Saviqmzanetti, how does it waste time?09:11
Saviqmzanetti, IMO, the time saved when you forget something that will prevent an out-of-source build09:12
Saviqis worth it09:12
Saviqwe just need to know about as many failures that might bit us in CI as possible09:12
Saviqand as soon as possible09:12
Saviqnic-doffay, hangout?09:15
nic-doffaySure Saviq09:15
Saviqmzanetti, looks like it worked http://s-jenkins:8080/job/unity-phablet-ci/09:37
Saviqmzanetti, only source is unavailable for some reason09:39
mzanettiSaviq: yeah... because real coverage and qml coverage are not build in the same step any more (I think)09:40
mzanettiSaviq: but it didn't add any real value anyways09:40
Saviqmzanetti, why?09:40
mzanettiSaviq: oh... its gone for c++ too09:40
Saviqmzanetti, yeah09:40
mzanettiI thought only for qml09:40
Saviqmzanetti, was it ever there for qml?09:41
* Saviq might not have checked09:41
mzanettiSaviq: yeah... for some reason it started working once I enabled the c++ one09:41
tsdgeosSaviq: mzanetti: Can you have a look at https://code.launchpad.net/~aacid/unity/remove_proxymodel_rolenames/+merge/158307 ? I've invited Florian to it too, but not sure he'll find a moment09:45
mzanettiSaviq: the whitespace thing should print which lines09:45
mzanettiSaviq: or just fix them09:45
Saviqmzanetti, to "just fix them" you can have a bzr hook, but the test should not do it09:46
Saviqmzanetti, it'd have to push back to the branch ;)09:46
mzanettiSaviq: yeah, sure, not in the test... but somewhere09:46
Saviqmzanetti, but lineno, sure09:46
Saviqmzanetti, http://doc.bazaar.canonical.com/plugins/en/text-checker-plugin.html09:46
mzanettiSaviq: qtcreator does not remove them :/09:46
Saviqmzanetti, it should09:46
* Saviq checks09:47
mzanettiSaviq: it does only in files he thinks belong to the project09:47
mzanettiSaviq: but since we're using CMake + qml...09:47
Saviqmzanetti, just open the qmlproject, no?09:47
mzanettiSaviq: ok... qtcreator tries, but it doesn't work everywhere09:48
dednickCimi: ping09:49
Cimidednick, pong09:49
mzanetti(which is news to me too)09:49
dednickCimi: did you ever manage to get findChild working with the timer?09:49
Saviqmzanetti, see, that's thanks to the whitespace test ;)09:49
Cimidednick, I didn't try09:49
Saviqmzanetti, but yeah, I agree it would be nice to print out lines09:49
mzanettiSaviq: tbh thats one thing I already hated in Qt gerrit09:49
Cimidednick, I saw it was not working, so I moved to readonly properties09:49
dednickCimi: ok09:49
dednickCimi: thanks09:49
Saviqmzanetti, at least here you can run the test locally and know straight away :D09:50
mzanettiSaviq: yeah09:50
Saviqmzanetti, gerrit is git, doesn't git complain about whitespaces anyway?09:50
mzanettiSaviq: no09:50
Saviqmzanetti, I think it's built-in, but configurable09:51
dednickmzanetti: question about public/private properties. There is a timer in MenuContent which has a 5 second interval for stopping the indicator menus. I want to test this behaviour, but dont really want the tests to wait for 5 seconds. What's the best course of action here?09:59
dednickunless it's just to suck it up and wait.10:00
mzanettidednick: yeah... good one... Problem is that Timers can't be found by findChild(). If possible, try to find another way to get a pointer to it out of the qml context to modify the interval for the test10:00
mzanettidednick: waiting 5 secs is not an option10:00
mzanettidednick: I'm thinking about adding a "interval" property to some other element in the code file and make the timer point to that10:01
dednicki think my head just exploded. ok. i'll give it a go :)10:01
mzanettidednick: huh?10:02
dednickmzanetti: yeah, i thoush about the interval property10:02
dednickmzanetti: about fishing it out of the qml context.10:02
mzanettidednick: tell me which file it is and I'll paste an example snippet10:02
dednickmzanetti: MenuContent.qml10:03
tsdgeossigh, this listview Qt bug is getting annoying10:04
tsdgeosnow one of the guys wants to make so that you have a "forceLayout" function in the listview you have to call if you want to make sure stuff like currentItem returns the correct value10:04
mzanettidednick: I think in this case it would make sense to add a public "property int contentReleaseInterval: 5000" and make the timer point to it10:05
dednickmzanetti: ok sure. thanks10:05
mzanettitsdgeos: hehe... the SignalSpy bug seems to be gone with 5.0.1 though10:06
tsdgeoscool :-)10:06
tsdgeosnow let's update to 5.0.2 :D10:06
tsdgeosSaviq: what'd be the correct blueprint "milestone" for that new hud task? Work items for ubuntu-13.04-month-5:?10:08
Saviqtsdgeos, -610:08
tsdgeoswhy 6?10:09
didrockstsdgeos: ubuntu-13.04-month-5 would mean you did it last month ;)10:11
didrockstsdgeos: it's an offset from the release schedule10:11
didrocksmonth 1 in developping raring10:11
didrocksand so on…10:11
Cimimzanetti, not really sure what to test of LensView if not the Timer10:11
didrockstsdgeos: yeah, let's make it not easy, right? :p10:12
Cimithe signals are emitted externally10:12
* mzanetti opens LensView.qml10:12
mzanettiCimi: yeah... there's really only that timer...10:17
mzanettiCimi: I'd say let it be...10:18
mzanettireally doesn't look like anything useful can come out of that10:19
Saviqmzanetti, https://code.launchpad.net/~saviq/unity/phablet.improve-check-whitespaces/+merge/15832510:30
CimiSaviq, wouldn't be easier to simply remove trailing whitespaces?10:37
SaviqCimi, no10:37
SaviqCimi, we would have to push back to the branch10:37
SaviqCimi, we don't want to do that10:37
Cimido we need them? :)10:37
SaviqCimi, no we don't, but that's our responsibility to not have them10:37
SaviqCimi, so whenever you run `make test` you'll know10:37
CimiSaviq, qtcreator removes them automatically for me10:37
SaviqCimi, yeah, sure, but that's not reliable enough10:38
mzanettiCimi: Saviq: does not work all the time10:38
SaviqCimi, and now you can just `make test` and you'll know10:38
SaviqCimi, and there's http://doc.bazaar.canonical.com/plugins/en/text-checker-plugin.html for those that want to automate tings10:38
Saviqthings, even10:38
Cimimzanetti, to me it always worked10:38
SaviqCimi, but not everyone uses qtcreator, not for everything10:39
SaviqCimi, and we have non-Qt code in the tree now, too10:39
mzanettiCimi: open a file and do: Ctrl+A, Ctrl+I, Ctrl+B... you'll end up with a few10:39
mzanettialso for very simple changes I don't use qtcreator but some command line editor10:40
mzanettididrocks: [mzanetti] document what apps can run on the desktop: TODO10:43
mzanettianything still needed?10:43
didrocksmzanetti: I don't think more is needed, do you mind checking with mterry, cyphermox, robru, ken if they have all the autopilot tests they need to be run?10:44
mzanettididrocks: all of the projects I've ever been involved have a -autopilot package10:45
didrocksmzanetti: excellent, that's what we needed, so yeah, you can mark it as DONE10:45
mzanettididrocks: ack10:45
mzanettididrocks: (apps and shell, that is)10:46
=== MacSlow is now known as MacSlow|lunch
dednickdont suppose anyone knows how to use a debugger with a qml file?11:05
dednickgetting an odd segfault11:05
Cimimzanetti, any convention on the function we want to use to call before each test? like a particular initTest?11:06
dednickand gdb is less than usefull when it comes to qml stacktraces.11:06
mzanettiCimi: no11:06
mzanettidednick: yep11:06
Cimimzanetti, initTest is already used?11:06
Cimimzanetti, or I should skip the word Test?11:06
mzanettiCimi: dunno... I haven't use one so far11:06
mzanettiCimi: probably skipping the word test makes sense, yes11:07
mzanettiCimi: oh... btw11:07
Cimimzanetti, tst_Showable uses init_test11:07
mzanettiCimi: for Qt in C++ if you have a function "void init()" it will be automatically called before each testcase11:07
mzanettiCimi: try that11:07
mzanettiCimi: and in C++ if you have one called "void initTestCase()" it'll be called automatically before the whole suite (I know... naming seems reversed)11:08
mzanettiCimi: same for cleanup() and cleanupTestCase()11:08
Cimimzanetti, in case we can improve tst_Showable11:08
Cimimzanetti, try renaming init_test to init()11:09
Cimiremove the function calls11:09
mzanettiCimi: I don't know if that works in QML too tho... you would need to test if first11:09
Cimiand add a console.log :)11:09
Cimisure I am doing11:09
Cimibefore I need to finish my test11:09
Cimihow can I See how qmltestrunner is running with the imports?11:16
CimiI am in tests/qmluitests/Dash11:16
Cimiand I added11:16
Cimiadd_qml_test(LensView IMPORT_PATH ${CMAKE_SOURCE_DIR}/plugins)11:17
Cimiin order to import11:17
CimiUnity 0.111:17
Cimiwhich didn't work11:17
mzanettitsdgeos: I just looked at your MP regarding the roles11:24
tsdgeoswhatcha think11:24
mzanettitsdgeos: I *think* there has been an issue in early QML days (Qt 4.7) where a proxy model had to have its own role names. at least I remember having to do that back in the days11:24
mzanettithat might explain why this code was here11:25
mzanettitsdgeos: I think your MP is ok nowadays11:25
Cimiwith import builddir/plugins imports something11:25
Cimibut then complains11:25
Cimi undefined symbol: _ZTIN5unity4dash13PeoplePreviewE)11:25
Cimitime to recompile unity?11:25
mzanettitsdgeos: especially since you with qt5 roleNames is a virtual method instead of a "setRoleNames()" thingie and you already directly forward stuff i'm quite sure its ok11:26
tsdgeosthat's my thought too11:27
mzanettitsdgeos: +1'd it11:27
tsdgeosSaviq: which was the ppa you used that made valueselectors work?11:30
Saviqtsdgeos, ppa:ubuntu-sdk-team11:31
CimiSaviq, builld_unity is missing libibus11:31
mzanettisomeone please re-review this: https://code.launchpad.net/~mzanetti/unity/phablet-test-people-preview/+merge/15832911:42
tsdgeoswhat happened to the other?11:44
mzanettitsdgeos: I wasn't able to merge it any more...11:44
mzanettitsdgeos: it complained about missing includes somewhere in unity and I couldn't figure why11:45
tsdgeosi'll do it after lunch, ok? ~1 hour aprox11:45
mzanettiI guess by then its full of conflicts again :D11:45
mzanettior rather :(11:46
mzanettibut sure... enjoy your lunch11:46
Saviqgreyback, there's an import issue with LVWPH test11:57
Saviqgreyback, ../../Components doesn't import11:57
greybackSaviq: yep just pushing fix now11:58
Saviqgreyback, tks11:58
greybackSaviq: pushed11:58
mardyluv: hi! I just noticed that SignOn::Identity has a signOut() method, and a quick look at the implementation suggests me that it should be working12:04
luvmardy: hey! thanks! .... strange? I played with that from python too (and indeed I stored the results afterwards and all that) but to no result (though I used the gi python bindings  - maybe that's the problem :-/ )12:06
luvwould signOut delete the credentials or just signout (ie delete current token (or whatever is appropriate) and tell the apps using the account to log out)?12:06
=== greyback is now known as greyback|lunch
=== MacSlow|lunch is now known as MacSlow
SaviqCimi, that might be a new requirement? what fails?12:08
CimiSaviq, nux12:08
SaviqCimi, you're on quantal?12:08
SaviqCimi, we're not building nux on raring12:08
CimiI am not sure though12:08
Cimiwhy is it?12:08
* Cimi redoes the thing again12:09
SaviqCimi, 'cause nux in raring is new enough12:12
SaviqCimi, it's not so in quantal12:12
CimiSaviq, I might had an old build script12:12
SaviqCimi, but when we switch the phone builds to raring we'll probably drop quantal support anyway12:12
CimiI'm redoing from phablet12:12
luvok, let mse see the code12:12
luvumm, I wont be able to untill I get home, the browse functionality here https://code.google.com/p/accounts-sso/source/browse/#git is not working12:13
dandraderSaviq, I don't think the current add_qml_test (in CMake) would support two IMPORT_PATH parameters would it?12:17
Saviqdandrader, it doesn't now, but should be really easy to add12:17
Cimiwho can help me with the issue above?12:18
dandraderSaviq, cool. will look into it12:18
Saviqdandrader, http://www.cmake.org/cmake/help/v2.8.9/cmake.html#module:CMakeParseArguments that's important12:18
Cimiadd_qml_test(LensView IMPORT_PATH ${CMAKE_SOURCE_DIR}/builddir/plugins)12:21
Cimiimport Unity 0.112:22
SaviqCimi, why would you import Unity in a test?12:24
Saviqyou need to fake the Unity plugin12:24
SaviqCimi, we can't import the actual Unity plugin in a test12:24
Saviqtsdgeos, could we have a test for https://code.launchpad.net/~aacid/unity/remove_proxymodel_rolenames/+merge/158307 ?12:25
Saviqtsdgeos, and move the tests for it under tests/ while we're at it?12:26
CimiSaviq, to use lenses?12:27
SaviqCimi, we can't12:27
SaviqCimi, you can't use the actual lenses in a test12:27
Cimiit worked for the DashBar12:27
Cimilike two weeks ago12:28
SaviqCimi, that doesn't mean it's right12:28
Ciminow doesn't work anymore though12:28
SaviqCimi, you need to fake the Unity plugin and whatever the LensView requires of it12:28
CimiI should write what, a mock plugin just for the test?12:28
SaviqCimi, yes12:29
paulliuhi. How can I run a specific test rather than make alltests.12:30
Saviqpaulliu, `make testComponentName`12:30
paulliuSaviq: ok. thanks12:30
Saviqpaulliu, i.e. `make testOpenEffect`12:30
Saviqpaulliu, when you've added the test with add_qml_test() macro12:30
SaviqCimi, and you wouldn't be the first to have done sone, tsdgeos wrote a fake HudClient plugin for the Hud tests12:30
SaviqCimi, that's just what you do12:30
CimiSaviq, I will do, after learning how to write a plugin and C++ :)12:31
SaviqCimi, look at test/qmluitests/Hud/qml12:31
CimiSaviq, already digging12:32
=== _salem is now known as salem_
Saviqtsdgeos, https://code.launchpad.net/~saviq/unity/phablet.fix-run_on_device/+merge/15834812:41
=== greyback|lunch is now known as greyback
tsdgeosSaviq: which test do you want for https://code.launchpad.net/~aacid/unity/remove_proxymodel_rolenames/+merge/158307 ? the existing test already has some regarding rolenames12:56
Saviqtsdgeos, sorry, didn't check12:56
mzanettiSaviq: hey, I'm having troubles testing Dash/People/Data and Delegate12:57
mzanettiSaviq: I don't really get what the Data is actually doing12:58
Saviqtsdgeos, right, could you then just move it to where it belongs, under tests/?12:58
tsdgeosSaviq: same commit?12:58
mzanettiSaviq: to me it seems like its just a container where we set data from the outside and use it again. Don't see where the DeeVariantText actually comes in12:58
Saviqtsdgeos, yeah12:58
Saviqtsdgeos, and actually, shouldn't we drop setRoleNames() from there?12:58
Saviqtsdgeos, it's deprecated, no?12:58
tsdgeosSaviq: i dropped it12:59
Saviqtsdgeos, from the test I mean12:59
tsdgeoswell the tests needs it to have a way to set roles to the mock model12:59
tsdgeosi think it's fine12:59
Saviqtsdgeos, right12:59
Saviqmzanetti, Data.qml unserializes the GVariant string12:59
tsdgeosi can rename it if you want12:59
tsdgeosso that it does not "collide" with the deprecated method13:00
Saviqtsdgeos, might be good to avoid13:00
tsdgeosand it's more obvious it's a "local" method13:00
Saviqmzanetti, and then looks through it13:00
Saviqmzanetti, and sets some properties on itself13:00
mzanettiSaviq: yeah, thats the thing... I can't see where we are actually using that...13:00
mzanettiSaviq: it looks like there is column_0 .. column_n coming from the model13:00
mzanettiSaviq: we set that on the Data, and just read it again in the delegate13:01
Saviqmzanetti, yeah, and we "convert that" into meaningful names13:01
Saviqmzanetti, but then we also read stuff like the phone number, email addresses and social statuses13:01
Saviqmzanetti, from the GVariant string13:01
tsdgeosSaviq: about the run_on_device thing13:02
Saviqmzanetti, and set those on the meaningful named properties13:02
tsdgeosit's failing to find boost_regex here13:02
tsdgeosprobably because it's a new dependecy13:02
Saviqtsdgeos, yeah, that's why the release13:02
tsdgeosand hte build-dep of the old package fails13:02
tsdgeoswill manually install13:03
Saviqtsdgeos, that and libgtest-dev13:03
mzanettiSaviq: I might just leave that one test to you :D13:03
Saviqmzanetti, Data.qml can actually be tested separately13:03
Saviqmzanetti, just so you know, all of that should go away (and happen in the backend)13:04
mzanettiSaviq: oh... then it probably doesn't make sense writing a test now at all13:04
Saviqmzanetti, yeah might be13:05
Saviqmzanetti, as it's the backend that should just give us all the values prepared13:05
mzanettiSaviq: given the indaba thing is a giant mess right now and most likely will be rewritten...13:05
mzanettiSaviq: do backends actually have to be written in vala or could we use Qt for those too?13:05
Saviqmzanetti, if you build Qt bindings for them...13:06
Saviqmzanetti, but anyway they won't be vala for much longer13:06
Saviqmzanetti, and AFAIK we don't want them in Qt, either13:06
Saviqwho cares13:06
Saviqif there's going to be a C and a C++ API, if there's bindings for Qt13:07
Saviqwe can just as well build them in Qt13:07
Saviqmzanetti, but anyway, not our part of the cake :)13:07
mzanettiSaviq: ah ok...13:07
mzanettiok... I'll strikeout the Delegate and Data then13:07
Saviqyeah that's fine13:07
tsdgeosSaviq: moved the test and renamed the method13:20
Saviqtsdgeos, cheers13:20
tsdgeosand pushed to the wrong branch13:20
Saviqtsdgeos, yeah ;)13:20
Saviqtsdgeos, does not contain a CMakeLists.txt file.13:22
mzanettihere's another way of increasing test coverage :D https://code.launchpad.net/~mzanetti/unity/phablet.remove-unused-header/+merge/15836413:22
tsdgeosdoes not?13:22
tsdgeosSaviq: pushed13:23
Saviqtsdgeos, yup13:24
Saviqmzanetti, :)13:24
mzanettiok then... bbl13:24
Cimigreyback, tried my mail?13:43
greybackCimi: no actually I haven't. I'll have a play once I've written up the API proposal13:44
=== dandrader is now known as dandrader|afk
tsdgeosCimi: btw if you need some help with the fake plugin, try copying mine from the HUD and if you don't understand something just give me a shout13:50
didrocksmterry: you can deploy whenever you want :)13:50
Cimitsdgeos, ok thx :)13:50
mterrydidrocks, k, waiting for it to automerge.  I'm manually patching enough things today13:51
didrocksmterry: it's merged13:52
didrocks(you mean cupstream2distro?)13:52
mterrydidrocks, oh!  well then13:52
mterrydidrocks, yeah13:52
didrocksmterry: I just skimmed over the emails at the minute it was sent! ;)13:52
mterrydidrocks, you're faster than thunderbird13:52
mterrydidrocks, though I suppose that's not saying much  ;)13:52
Saviqtsdgeos, should we just go for "setRoles"?13:53
tsdgeosSaviq: ok13:53
mterrydidrocks, is there a way to run cu2d-update-stack -U on the whole set?13:54
didrocksmterry: yeah, I'm not sure to like the comparison ;)13:54
tsdgeosSaviq: done13:54
didrocksmterry: no :/13:54
Saviqtsdgeos, thanks13:54
mterrydidrocks, should I be running it on the changed phablet ones too?13:54
didrocksmterry: well, if you ran it on your desktop, it's good enough13:55
didrocksmterry: I think we'll still have some FTBFS TBH13:55
didrocksmterry: so let's figure them out first ;)13:55
mterrydidrocks, yes, we will have ftbfs.  But I meant should I be running it on the cfg files under phablet/13:55
jibeldidrocks, I didn't create the 'network' view, there is no job with this name and the name of the stack is 'location' in the configuration file13:56
didrocksmterry: oh not under phablet13:57
didrocksmterry: we never deployed it13:57
mterrydidrocks, ok13:58
didrocksjibel: network and locations are differents13:58
didrocksjibel: let me deploy it quickly, sorry for missing it13:59
didrocksjibel: done13:59
jibeldidrocks, I guessed so, that's why "name: location" in network.cfg sounds weird13:59
=== dandrader|afk is now known as dandrader
didrocksjibel: no, it was exactly what I wanted to do… hem :p14:02
mterrydidrocks, jibel: when trying to deploy, I keep getting connection timed out errors (but, like, midway through).  Any known issues with jenkins?14:07
didrocksmterry: oh? not that I know of or saw today even14:09
jibelmterry, which stack? always the same or different one each time? can you paste the full output of the command?14:10
mterryjibel, sure14:10
mterryjibel, I got this with both the apps and platform stacks: http://pastebin.ubuntu.com/5698566/14:10
mterryjibel, I assume I'd get it with more, can try if you want14:10
mterryIt's reliable14:11
=== dednick is now known as dednick|lunch
ChrisTownsendIs there even a chance that the fix for https://bugs.launchpad.net/compiz/+bug/763148 is SRUable for 12.10 and more importantly, 12.04?14:40
ubot5Launchpad bug 763148 in Compiz 0.9.9 "Adding/Removing an external monitor causes open windows to move to another workspace" [Medium,Triaged]14:40
=== francisco is now known as Guest35830
didrocksfginther: does      indicator-icons still change?14:46
didrocksfginther: I think the icons are merged in ubuntu-themes14:47
fgintherdidrocks, there hasn't been a merge since Feb 2014:55
didrocksfginther: yeah, can you kill it please?14:55
fgintherdidrocks, no problem14:55
=== dandrader is now known as dandrader|lunch
Cimitsdgeos, what calls fake_libhud_client?15:04
=== dednick|lunch is now known as dednick
tsdgeosCimi: not sure what you mean15:12
Cimitsdgeos, I'm studying the plugin15:12
Cimitsdgeos, fake_hud_plugin registers15:12
Cimitsdgeos, libhud_client_stub is the code of the plugin registered by fake_hud_plugin15:13
Cimitsdgeos, I'm wondering when all the processing in lin fake_libhud_client happens15:13
smspillazChrisTownsend: probably, the code change is not too complicated15:13
smspillazChrisTownsend: ask the distro team15:13
tsdgeosCimi: when those functions are called15:13
tsdgeoswhat i'm doing there is implement a stub of the libhudclient15:13
tsdgeosso i'm "implementing" the functions of the real libhudclient15:14
tsdgeosthey are called from plugins/HudClient/*15:14
ChrisTownsendsmspillaz: Thanks.  Yeah, I'll follow up with them.  If they think it's ok, then I'll work on backporting it.15:14
dednickCimi: the plugin path that is test in the test overrides the default hudclient path, so it's loaded instead of the one from plugins/HudClient.15:14
dednick*set in the test15:15
tsdgeosanyone has any idea why ./run_on_device is not syncing one of my files? (it's new)15:15
dednickCimi: so when tst_hud.qml does "importHudClient 0.1" it's loading from the qml folder, where the HudClientStub is registered15:16
Cimiah ok15:16
dednickthe Panel does it as well, except with qml files instead of a library.15:17
tsdgeosok, needed to bzr add them15:18
tsdgeosmzanetti: what happened? https://code.launchpad.net/~aacid/unity/remove_proxymodel_rolenames/+merge/15830715:30
* mzanetti checks15:30
mzanettitsdgeos: thats a bit unfortunate and shouldn't happen... the mediumtests-builder job failed15:30
mterryfginther: any ideas on that jenkins timeout?15:30
mzanettitsdgeos: 16/16 Test #16: cleanincludes ........................***Not Run   0.00 sec15:32
mzanettitsdgeos: full log: http://s-jenkins:8080/job/generic-mediumtests-builder/1097/console15:32
tsdgeosmzanetti: oh i see :-/15:33
mzanettitsdgeos: do you know what failed?15:34
mzanettitsdgeos: actually the generic-mediumtests-builder should never fail if the other ci jobs pass - that's why it has been hidden in the comment that jenkins posts15:34
fginthermterry, are you referring to tsdgeos' build?15:34
mterryfginther, sorry no, I was trying to deploy a new config earlier15:35
mterryfginther, I was getting timeout errors15:35
mzanettitsdgeos: since yesterday I've seen some of the new API team tests fail only on that one... no idea yet what exactly happens15:35
* fginther checks the logs15:35
mterryfginther, sorry15:36
mterryfginther, I meant to ping jibel15:36
mterryfginther, for some reason I remembered it as you15:36
=== jhodapp is now known as jhodapp|lunch
mterryjibel, any ideas on that jenkins timeout?  (nailed it!)15:36
tsdgeosmzanetti: no i don't15:37
tsdgeosit was a "i see" of "i couldn't find what failed"15:37
mzanettijussi might have an idea... he wrote that test15:37
tsdgeosmzanetti: but "not run?"15:37
tsdgeosi "could" understand not passed15:37
mzanettitsdgeos: it says BAD_COMMAND15:37
tsdgeosbut not run...15:37
mzanetti2 lines down15:38
mzanettiwhatever that means15:38
tsdgeosbinary not available?15:38
mzanettitsdgeos: its a python script15:39
mzanettitsdgeos: but so is the whitespace one, and that passed15:39
* tsdgeos shrugs15:39
Saviqmzanetti, tsdgeos, autolanding / ci has python15:42
Saviqmzanetti, tsdgeos, but pbuilder does not15:43
mzanettiyeah... I know15:43
Saviqor PPA, rather15:43
mzanettiSaviq: do you know what "test not run (BAD_COMMAND)" means?15:43
Saviqmzanetti, yeah, python3 wasn't there15:44
mzanettiok... I know whats happening then15:44
Saviqmzanetti, tsdgeos https://code.launchpad.net/~saviq/unity/phablet.add-python3-dep15:44
* mzanetti fixes15:44
Saviqor https://code.launchpad.net/~saviq/unity/phablet.add-python3-dep/+merge/158398 rather15:44
tsdgeosmzanetti: i'd give it a "broken hardware" thing15:45
tsdgeosi mean that test run when it was autolanded15:45
mzanettitsdgeos: the mediumtests builder can run on precise machines, while the other only run on quantal & raring15:45
mzanettitsdgeos: I'll restrict the builder to quantal and see if that helps15:46
tsdgeosweird :D15:46
mzanettitsdgeos: indeed... jenkins config says it should be restricted on quantal-i386.. yet it ran on a precise machine.15:49
mzanettitsdgeos: but I guess the precise machine has a quantal pbuilder chroot which makes it qualify for that15:49
mzanettiyep... also the other quantal builds run on precise hosts... so thats not the issue15:50
mzanettinow I'm really puzzled why it fails only in there and not everywhere15:50
mterrydidrocks, any word on jenkins/deploying feasibility?15:51
jibelmterry, no idea, I cannot reproduce it and no error message in servers logs16:00
mterryjibel, oh.  :(  will try again16:03
mterrydidrocks, I guess there is some mterry-specific error with jenkins deployment right now.  Can you deploy -config trunk for me?16:11
didrocksmterry: sure, what stacks?16:11
mterrydidrocks, stacks/head/hud.cfg16:19
didrocksyou have made that many changes?16:19
didrockslike location is empty16:19
didrocksI already deployed it this morning :p16:19
mterrydidrocks, then not that one.  I was just working off the list of modified files when I did a bzr pull16:20
didrocksmterry: ok, deploying them one afoter another16:21
Zhenech /wi6016:21
mterrydidrocks, is there a reason we couldn't automate it?16:21
didrocksmterry: we need to first poke if the stack is running16:21
didrocksmterry: because if the stack is running, it needs to wait before deploying16:22
mterrydidrocks, I mean, we still need the atchive-admin bit.  but we should always deploy after a change, right?16:22
mterrydidrocks, how about right before a stack runs, it deploys itself16:23
didrocksmterry: if you have a patch for that, I would be happy :)16:23
mterrydidrocks, not today, anyway.  I think I'll just keep having you deploy for me until you get tired of it and patch it yourself.  ;)16:24
didrocksmterry: or get your machine fixed?16:25
mterrydidrocks, yeah, I wonder why only I get this error16:25
=== dandrader|lunch is now known as dandrader
mzanettiSaviq: you have an idea what could be happening here by any chance?16:57
mzanettiQXcbConnection: XCB error: 148 (Unknown), sequence: 148, resource id: 0, major code: 140 (Unknown), minor code: 2016:57
mzanettiand the application never finishes to initialize16:57
=== jhodapp|lunch is now known as jhodapp
mzanettisuper simple MP anyone? https://code.launchpad.net/~mzanetti/unity/phablet-bring-back-launcher-tests/+merge/15843417:19
Saviqmzanetti, on it17:19
Saviqmzanetti, about the xcb error, no :/17:19
mzanettiSaviq: FYI: I have no clue why, but code contents in cobertura reports are back17:33
Saviqmzanetti, yay!17:34
mzanettiSaviq: and there is really not much red in our testing doc any more17:34
Saviqmzanetti, yup17:34
mzanettitomorrow I'll check the state of our ListItems17:34
mzanettiI'm a bit afraid of the Dashs17:35
mzanettibut most likely because I haven't tought good enough about how to test them yet....17:35
mzanettiSaviq: I commented on Shell.qml in the testing doc. when you have a minute think about it and let me know if you agree. Not necessarily today any more.17:37
mzanettiI'll call it a day now17:37
Saviqmzanetti, any more? ;)17:37
Saviqmzanetti, cheers17:37
Saviqmzanetti, still around?17:58
Saviqmzanetti, if you are, can you look at
Saviqsergiusens, or you ^?17:59
sil2100mterry, mzanetti: sorry for again messing up the work items in the blueprint! Had a misunderstanding with firefox ;) But I think it's all ok now18:01
mterrysil2100, heh, I do it all the time18:01
kgunnmterry: hey, so one item that needs to get added somewhere is "hint where launcher is" from greeter18:23
kgunnshould that be an item for launcher? greeter? or just the shell ?18:24
mterrykgunn, I'd say greeter.  Design is looking at various ways to hint both launcher and right-side swipe from the greeter, so they may come up with a related fix for both18:25
mterrykgunn, I'll add18:25
kgunnmterry: you are awesome...18:25
mterrykgunn, there is a "discover edges" item under greeter that I will expand for that18:25
kgunnmterry: ah...just saw it18:25
kgunnmterry: actually nic d'offay will own the ui portion of the infographic  & pete's gonna own the backend18:27
mterrykgunn, OK.  I'm still grappling with the engineers involved, thanks18:27
mterrykgunn, I didn't have to care before  ;)18:27
sergiusensSaviq: looking18:36
mterrykgunn, do you know which teams/engineers are working/available for other OOBE stuff, like the installer and first-time customizations?18:37
kgunnmterry: no i'm not...if it needs to be done, add it, then add a note saying no owner18:38
mterrykgunn, k18:38
=== dandrader is now known as dandrader|afk
sergiusensSaviq: is this /tmp/qmlfile.qml something you talked about with mzanetti?18:56
mzanettisergiusens: whats whit it?18:56
sergiusensmzanetti: can't find that file in the tests and aborts it seems18:56
sergiusensmzanetti: my first hunch18:56
mzanettisergiusens: oops. I'll fix it18:57
sergiusensmzanetti: is it supposed to be in the hook?18:57
mzanettisergiusens: no...18:57
sergiusensmzanetti: ps-quantal-server-amd64-1 is offline in jenkins and started if you want to look into it18:57
mzanettisergiusens: ah ok... thats why I can't reach it18:58
sergiusensmzanetti: just ssh into it :-)18:59
mzanettisergiusens: no. need to change the job config18:59
sergiusensmzanetti: so you have qmlscene /tmp/qmlfile.qml & and also set -e and [ -f /tmp/qmlfile.qml ] is false18:59
sergiusensmzanetti: I'll put the machine online again and stop it from virsh if you don't think you'll need it19:00
mzanettisergiusens: fixed19:00
Saviqmzanetti, thanks19:01
sergiusensmzanetti: node is back19:01
mzanettisergiusens: so the problem is this: I haven't yet found out why, but sometimes the very first run of a Qt5 app in the VM just hangs19:01
mzanettisergiusens: I had that already with the mediumtests in the i386 vm's19:01
mzanettisergiusens: I just couldn't find the solution so I added a workaround that just fires up qmlscene and kills it again.19:02
Saviqsounds reliable :D19:02
mzanettisergiusens: worked like a charm. at some point I noticed it wasn't required any more and removed it again19:02
mzanettinow the same thing started on the amd64 vms19:02
sergiusensmzanetti: great, at first I thought you were doing environment validation before running anything19:02
mzanettiSaviq: its the xcb error I posted earlier19:03
sergiusensmzanetti: do you have a log with the error?19:03
mzanettisergiusens: yep, one sec19:03
mzanettisergiusens: this is the line: QXcbConnection: XCB error: 148 (Unknown), sequence: 148, resource id: 0, major code: 140 (Unknown), minor code: 2019:03
mzanettisergiusens: everything else is exactly the same as with successful runs19:04
mzanettisergiusens: if it hangs, it stalls at this line19:04
=== dandrader|afk is now known as dandrader
sergiusensmzanetti: this does ring a bell... I'll see if I create a vm on my machine19:07
sergiusensmzanetti: other topic, where is our current autopilot branch these days?19:17
sergiusensand how close are you with autopilot-1.3?19:18
Saviqmzanetti, we crossed the mark of 200 tests :D19:25
bschaeferSaviq, yay. Would you want something like this in ./run? As running things in gdb is slightly annoying atm.19:28
bschaeferSaviq, http://paste.ubuntu.com/5699506/19:28
Saviqbschaefer, sure, looks useful, only thing is that I'd probably drop the UNITY_CORE...19:30
mzanettiSaviq: \o/19:30
Saviqbschaefer, export LD_LIBRARY_PATH19:30
Saviqmzanetti, yup19:30
mzanettiSaviq: another 200 and we are gaining on Mir :P19:30
bschaeferSaviq, soo have the users do the export?19:30
bschaeferor have it in the bash script19:31
Saviqbschaefer, no no, in the script19:31
bschaeferSaviq, alright, ill do a MP for that :)19:31
Saviqbschaefer, but export the var instead of just running qml with it19:31
Saviqbschaefer, and then run gdb directly, without the $OPTIONS var19:31
Saviqbschaefer, and please support -g, too19:31
Saviqbschaefer, and use getopt19:32
Saviqbschaefer, and we good!19:32
bschaeferSaviq, sounds good :), ill see what i can do19:32
Saviqbschaefer, one last thing - « gdb -ex run --args ... », please19:34
Saviqbschaefer, so that we don't have to type "run" manually19:34
bschaeferSaviq, o right, typing that r would get annoying if we can run it our selfs19:34
fginthercyphermox, what do I need to do to get https://code.launchpad.net/~fginther/cupstream2distro-config/qa-stack-update/+merge/158197 deployed?19:49
fginthercyphermox, the jenkins server looks quite19:49
bschaeferSaviq, heres what I have: https://code.launchpad.net/~brandontschaefer/unity/add-gdb-support-to-run-script/+merge/15846520:06
bschaeferworks well for me20:06
Saviqbschaefer, no need for the shift20:07
SaviqI _think_20:07
bschaeferSaviq, hmm the shift moves over one if an option is matched right?20:07
Saviqbschaefer, yeah, but we should get the "rest" from getopt20:07
SaviqI _think_, again20:07
* Saviq reads20:07
bschaeferSaviq, hmm well I also stole a bit of that code from ./build20:07
Saviqbschaefer, yeah, but that didn't have $@, so no worry there20:08
bschaeferSaviq, as I would think, if its ./run -g 1 2 3, and we hit a -g it shifts $@ = 1 2 320:08
Saviqbschaefer, whereas for ./run we need it20:08
bschaeferSaviq, correct, ooo you're saying it'll shift all the params20:08
bschaeferright, ill remove that and find an option for the qml_phone_shell to test it out if it gets the args or not20:09
Saviqbschaefer, just make sure that there's no "better" way for getopt20:10
Saviqto get "the rest"20:10
bschaeferSaviq, alright cool, let me do some more digging to make sure we get all the args from $@20:10
Saviqbschaefer, and maybe we should separate the args passed to qml-phone-shell with --20:10
bschaeferSaviq, hmm I could look into adding them to the run script20:10
Saviqbschaefer, to be somewhat "standard" compliant20:11
bschaeferor you're saying have a break20:11
bschaeferSaviq, i've actually never used getopts before soo let me read more of the man pages :)20:11
Saviqbschaefer, yeah, `./run -g -- --whatever --options --for --qml --shell`20:11
Saviqbschaefer, sure20:11
bschaeferSaviq, we should be able to stop eating args up when we hit a '--' that would be nice20:12
* bschaefer thinks there should be a better way possibly20:12
Saviqbschaefer, that might help http://serverfault.com/questions/95077/how-can-i-get-remaining-args-after-pulling-out-parsed-items-using-getopts20:13
bschaeferSaviq, you are very good at this google thing20:13
bschaeferhaha, thanks! Ill read through it :)20:13
Saviqoh, that's interesting http://rsalveti.wordpress.com/2007/04/03/bash-parsing-arguments-with-getopts/20:14
Saviqwe have ourselves a getopts master around :]20:14
cyphermoxfginther: can we also migrate gtester2xunit and pyruntest?20:14
rsalvetijezz, that's from 2007!20:14
bschaefero awesome20:14
fginthercyphermox, I don't have permissions to migration gtester2xunit (need Martin) and we don't want to continue support of pyruntest.20:15
fginthercyphermox, so if you want to wait until the other work can be done, I'm fine20:15
cyphermoxI'd rather it all be done yeahd20:18
fginthercyphermox, ok, I'll make a note in the MP20:19
cyphermoxincluding pyruntest if possible, if anyone wants to pick it back up then we can just keep doing just the fixes in a stable branch20:19
cyphermoxthomi: ^^ how do you feel about branching pyruntest for a stable branch?20:19
thomicyphermox: we're actually talking about deprecating pyruntest, since you can do everything with subunit & testtools20:20
cyphermoxyeah, but still ;)20:20
cyphermoxyou know, there might still be bug fixes even though it's attained perfection already ;)20:21
thomicyphermox: if someone else maintains it, that's fine with me, but I have too many projects on the go at once, and it's not particularly well written20:21
thomiOnce martin gets back I'll be pushing that we adopt subunit & friends as our standard way of running python tests20:21
bschaeferSaviq, one thing, is rsalveti example didn't shift the arguments out, but the other example has this: shift $(( $OPTIND -1 )) soo that should work nicely :)20:23
* bschaefer attempts20:23
bschaeferunless I missed something in his example :)20:23
fginthercyphermox, thomi, if we just need to create a '13.04' type branch, I don't have a problem with that. We can then remove it from head once it's removed from all projects?20:23
Saviqbschaefer, yeah20:24
bschaeferSaviq, cool, well ill be sure to poke you next when I have it working. Thanks for the links!20:25
=== seb128_ is now known as seb128
Saviqbschaefer, cheers20:30
=== salem_ is now known as _salem
bschaeferSaviq, when you get a chance: https://code.launchpad.net/~brandontschaefer/unity/add-gdb-support-to-run-script/+merge/15846521:09
bschaeferorder does matter, run options have to come before the qml-phone-shell options21:10
bschaefer(shift can't eat specific indexes)21:10
Saviqbschaefer, yeah, that's fine, didn't manage to get the -- to separate args to ./run from args to the binary?21:12
bschaeferSaviq, hmm well its not needed, but I can look into getting it that way21:12
bschaefer./run -g -frameless works21:12
Saviqbschaefer, yeah I know it's not needed, but it's the convention21:12
bschaeferSaviq, oo alright, let me get that in21:12
Saviqbschaefer, also, please bring back --gdb21:13
bschaeferSaviq, getopts can only do single options :(21:13
Saviqbschaefer, --longopts?21:13
Saviq--longoptions, actually21:13
bschaeferSaviq, hmm what I read, it can only do single21:13
bschaeferSaviq, http://stackoverflow.com/questions/402377/using-getopts-in-bash-shell-script-to-get-long-and-short-command-line-options21:13
Saviqbschaefer, we even have long opts in ./build and ./build_unity21:14
Saviqbschaefer, and you did have them before21:14
bschaeferSaviq, but it uses getopt21:14
Saviqah getopt vs. getopts21:14
Saviqbschaefer, use getopts, then21:14
Saviqas we do in the other scripts21:14
bschaeferyup, but I can look back at getopt and see if I can count up to N until we hit a --21:14
bschaeferSaviq, well the other scripts use getopt21:15
Saviqbschaefer, and they use --longoptions, I'm confused21:15
bschaeferSaviq, getopt can use --longoptions, getopts cannot21:15
bschaefergetopts loops through the options21:15
Saviqah got it, getopts is the bash thing21:16
Saviqwhile getopt is the cript21:16
* bschaefer is doing bad at explaining this21:16
Saviqconfused the two21:16
bschaeferSaviq, yeah, the 's', but I can see if I can get getopt working21:16
Saviqbschaefer, yeah, should work fine I imagine21:16
bschaefersince we will have an order of things, and stop when we hit an '--', and count up21:16
bschaefercool, let me play with that, im learning quite a bit about bash haha21:16
Saviqbschaefer, sorry to badger you like that, it's just a freakin' run script after all....21:17
Saviqbut while we're at it, we might just as well make it more useful :)21:17
bschaeferSaviq, haha, no worries, I would prefer to do it right :)21:17
bschaefershould be easy to add more options after this21:17
bschaeferSaviq, when you return, i've got the branch ready. It shifts until it hits a '--' then breaks, leaving the args after the '--' untouched21:58

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