=== sarnold_ is now known as sarnold [02:18] hello === Giovanni is now known as Guest10288 [02:18] hello [02:18] hell Guest10288 [02:18] hello even :) [02:27] !clear [02:27] Factoid 'clear' not found [02:27] there are italian? [02:31] SuperStep: check out #ubuntu-it [02:47] hello [03:19] ahayzen, pong [03:20] balloons, did u trigger a rebuild of https://code.launchpad.net/~andrew-hayzen/music-app/mediaplayer-simplify/+merge/201265 earlier? or did it randomly retest it? [03:20] balloons, also appears more things are passing, either due to the fixes u guys put in or some changes i made...but is now failing on a different thing http://91.189.93.70:8080/job/generic-mediumtests-trusty/1505/testReport/junit/music_app.tests.test_music/TestMainWindow/test_reads_music_library_with_mouse_/ [03:21] ahayzen, click the link, you can see the jenkins bot did it [03:21] I just kicked one, just for you :-) [03:21] balloons, no this one http://91.189.93.70:8080/job/music-app-ci/603/ [03:21] balloons, i made some changes as it had conflicts [03:22] ohh.. I had a way old page in my cache it was showing [03:22] lol [03:22] balloons, but now it is failing to read values from an array on an object [03:22] balloons, it should be able to do tht right? [03:22] ahayzen, this still has to land: https://code.launchpad.net/~veebers/autopilot-qt/reintroduce-exporting-qobject-children-of-qml-items/+merge/207581 [03:22] balloons, ah ok so maybe it was my reshuffle into Item {} tht caused some of them to be fixed [03:23] there were fixes, which causes regressions as you remember, then they backed it out.. but the new stuff is 2 mp's.. one landed, the other has not [03:23] balloons, hmm ok [03:23] it's going through the process and should land soon.. once it does, your tests should work [03:24] if we find they *still* don't work, we'll have another look of course.. if you wan to test now locally, simply grab that branch and overlay your local autopilot with it [03:25] balloons, just to confirm... self.player.currentMeta.artist ...would be the correct way to read artist from ... property var currentMeta: {"album": "", "artist": "", "cover": "", "title": ""} [03:25] ahayzen, I agree [03:25] there's also get_properties() [03:25] balloons, it fails with 'AttributeError: Class 'Player' has no attribute 'currentMeta'.' [03:26] balloons, which sounds similar to the other issue so i'll wait until tht has landed [03:26] ahayzen, variable property.. ohh it's late [03:26] something is triggering in my head on that [03:26] not sure what.. It's sleepy time :-) [03:27] balloons, yh i better go to bed lol 3am here :/ [03:27] ahayzen, :-) Ask again when we're sane [03:27] balloons, hehe thanks for ur help :) [03:27] good night [03:27] night [05:12] Good day all , , how to solve this problem ? http://pastebin.com/CGwRE3hn , cuda was installed before,see http://pastebin.com/V6GvK0dv [05:14] alabd: you need to install whichever of those packages will provide a library that can link with your program when you use -lcuda [07:48] nik90: ping === jackson is now known as Guest46812 [08:11] zsombi: pong [08:12] nik90: hi dude, I have a question on Clock app AP test: ERROR: ubuntu_clock_app.tests.test_clock.TestClock.test_label_value [08:12] nik90: seems this test is a bit flaky... [08:12] nik90: I have an MR with a fresh new component, where I see this failing, then another one with also a new component, and there passes... [08:14] nik90: here's the full log: http://paste.ubuntu.com/6998622/ [08:14] zsombi: I will take a look [08:15] nik90: thx === Guest46812 is now known as Noskcaj [08:19] good morning [08:25] zsombi: the error is not so much in the test but rather at the setup() itself [08:25] zsombi: I ran the test 5 times..but it didn't fail on me [08:25] zsombi: did you run on device or desktop? [08:25] nik90: on device [08:26] zsombi: It looks like the clock app most likely did not open [08:27] aham... :/ [08:27] zsombi: I believe this is happening sometimes for the AP tests of other apps as well..though happens only sometimes [08:28] nik90: well, let's monitor it and do something about it if needed [08:29] zsombi: I believe the QA is looking into it if I remember reading the emails about it [08:29] nik90: ah, ok :) [08:29] then we're good :) [08:29] :) [09:17] popey: the ubuntu emulator in qtcreator works beautifully -> http://i.imgur.com/D6fhihp.png [09:18] Nice! [09:18] zsombi: Hi, I have a problem with ConditionalLayout at app startup on the device. Seem like the correct width of the app is set too late, so the first render assumes the size set in MainView. [09:18] ooh, nice tutorial [09:18] zsombi: Which is bad when switching from tablet to phone factor [09:19] m-b-o: any snapshot of the code I can check? [09:20] zsombi: https://code.launchpad.net/~martin-borho/ubuntu-weather-app/anchors-refactoring I've refactored the anchors, but it also happens in trunk [09:21] Good morning all; happy For Pete’s Sake Day! :-D [09:22] zsombie: printing the width in Component.onCompleted it says on phone 1928, which is gu 107. [09:22] zsombie: when refreshing the data, the size is correct then [09:23] m-b-o: so the application starts with the ConditionalLayout active? [09:24] zsombie: yes. [09:24] zsombi: the same in clock app [09:24] m-b-o: zsombi, not zsombie :) can I get a link to the file itself and not to the MR? [09:24] yes, sorry :) [09:25] http://bazaar.launchpad.net/~martin-borho/ubuntu-weather-app/anchors-refactoring/view/head:/ubuntu-weather-app.qml [09:25] zsombi: and http://bazaar.launchpad.net/~martin-borho/ubuntu-weather-app/anchors-refactoring/view/head:/components/LocationTab.qml [09:26] m-b-o, zsombi: The clock app opens with the phone layout which is the default layout. I have only defined the conditional layout for tablets as suggested by zsombi. So essentially the conditional layout is not active at start. [09:26] nik90: but the your property signals tablet [09:27] nik90: wideAspect [09:27] m-b-o: well I defined a boolean property called wideAspect: width > units.gu(80) [09:27] m-b-o: so techinically that boolean property should be false on startup on the N4 [09:28] nik90: but it isn't... [09:28] nik90: m-b-o: the default layout is built up, all anchors are set, then the ConditionalLayout is activated immediately as the condition applies immediatelly [09:29] m-b-o: print out the Layouts.currentLayout on changed [09:30] zsombi: you mean oncompleted? [09:30] nopes, when Layouts.onCurrentLayoutChanged [09:31] zsombi: will take some miinutes... [09:33] m-b-o: so it be :) [09:33] I can eat sthing meanwhile :) [09:34] zsombi: enjoy! :) [09:34] thx [09:40] m-b-o: I just outputted the wideAspect value on the desktop, it starts of with true -> false .... the true is there for hardly a second [09:41] nik90: and on the device? [09:41] m-b-o: how do you see out the console output on the device? [09:41] m-b-o: I tried on the emulator, but it is not printing anything to console [09:44] "General Messages tab in QtcReator [09:44] m-b-o: what I did was I changed one of the labels in the UI to reflect the wideAspect variable [09:44] m-b-o: on the N4 it shows wideAspect: false [09:46] hi.. [09:47] hi [09:52] zsombi nik90: it changes on device from wide layout to phone layout, but the sidebar from tablet mode is still shown: http://imgur.com/vDtpO9E [09:53] m-b-o: I have a feeling the conditions for the sidebar are not properly updated with the window width [09:53] considering that the conditional layout switches to phone layout [09:53] actually it appears after one second [09:54] nik90: yes [09:59] hey guys, is there a file picker in the sdk? [10:02] ah, I've found documentation on the content stuff [10:12] m-b-o: so, your default layout is phone layout? [10:13] zsombi: no, tablet [10:13] m-b-o: I don;t get it... the conditional layout is for width > 80GU... [10:14] m-b-o: that's not the default one [10:14] zombie: yes/no... there was too much hassle last week. I guess, the default is phone, but it start has width, hieght for tablet in MainView [10:14] zsombI [10:14] :) [10:15] zsombi: okay, I see [10:15] m-b-o: so, the ConditionalLayout gets active only after the default layout is set up [10:16] zsombi: yes. but as ist starts in a size, which is not the default layout there's a problem [10:17] m-b-o: I think the size is ignored when you are running on device [10:18] zsombi: but Layouts.onCompleted has the condtionalLayout active first. Will try to start with phone sizes [10:19] m-b-o: have you printed out the Layouts.currentLayout when onCurrentLayoutChanged? [10:19] yes, nothing set [10:20] m-b-o: nothing set? you mean the value is empty? then it means it activates the default one [10:20] http://developer.ubuntu.com/api/qml/sdk-14.04/Ubuntu.Content.index/ <- I'm trying to use this example, but I'm getting an error each time [10:21] zsombi: yes, coming from the conditonal one, I assume [10:21] Error: Invalid write to global property "activeTransfer" [10:21] m-b-o: as teh condition does not satisfy [10:21] zsombi: when started with a width for phone (gu 50) Layout.onCompleted says it has the default one [10:22] m-b-o: do you have the logs? can you pastebin it [10:22] zsombi: one moment [10:23] http://paste.ubuntu.com/6999031/ <- any thoughts why line 43 is giving me Error: Invalid write to global property "activeTransfer" [10:24] SuperMatt: perhaps you should have "var " in front of it :) [10:24] fool me for copying an example [10:25] I wish people would confirm their examples work before uploading them [10:25] SuperMatt: actually you should have a property var activeTransfer somewhere declared [10:25] SuperMatt: and actually you have... [10:25] http://developer.ubuntu.com/api/qml/sdk-14.04/Ubuntu.Content.index/ <- I'm copying this [10:25] SuperMatt: line 55 [10:26] yeah, Isee [10:26] SuperMatt: yep... in these kind of situations it is good to give an ID to the Column, and reffer to the activeTransfer property using that ID. [10:27] lemme give that a try [10:27] SuperMatt: sometimes JS cannot detect the context, so you need complete reverence to that [10:27] zsombi: when starting with phone width http://paste.ubuntu.com/6999040/ [10:28] with with 107gu: http://paste.ubuntu.com/6999050/ (as in bzr) [10:28] m-b-o: both logs are from device, right? [10:28] yes [10:28] Good day all , , how to solve this problem ? http://pastebin.com/CGwRE3hn , cuda was installed before,see http://pastebin.com/V6GvK0dv [10:29] zsombi: when in tablet mode, it activates first the tablet mode, then default layout. but default layout becomes not visible [10:30] m-b-o: why are there two layouts? do you have 2 tabs? [10:30] zsombi: yes. [10:30] ok [10:32] the tabs are build dynamically by an ugly hack.... perhaps that's a problem Line 162: http://bazaar.launchpad.net/~martin-borho/ubuntu-weather-app/anchors-refactoring/view/head:/ubuntu-weather-app.qml [10:32] m-b-o: holly.... [10:33] m-b-o: revenge of Tabs :D [10:34] m-b-o: why don't you use Repeater to build the tabs? [10:34] m-b-o: it could be the problem, as I don't really see anything wrong in the layout you have [10:35] zsombi: haven't looked at it since autumn, but I have it on the list for refactoring..... :) [10:35] m-b-o: I know dynamic tabs was on the table long time, and it was landed then removed due to some failures on the Tabs whic ended up not being brought by that MP [10:36] m-b-o: right now it's approved again, and will come in one of the next releases, but the change we made back the were enabling Repeater to create tabs dynamically any time. [10:37] zsombi: that would be cool! I'll try with Repeater [10:38] zsombi: but don't you think width set in MainView should reflect the default layout? [10:38] it should, if it doesn't then the Tab/Page has some problems. You should not set anchors in Tab/Page as those automatically do [10:39] okay, noted. So I will switch the default layout to tablet. I'll give you a ping about the outcome! [10:39] m-b-o: btw, that strange Tabs creation may also cause problems on anchor transfering, so... :) [10:40] m-b-o: Beware of the leopard :D [10:40] is the content stuff actually implemented yet? I'm trying to test in qt creator and I just see the circle of friends go round and round and round and roud... [10:41] it looks cool, but it's not exactly helpful [10:41] zsombi: will add a comment line: "here be dragons". Should be alright then ;) [10:43] :D [10:50] I think I give up with a qt version of this app. I like writing in python, so I think I'll give pygtk a bash [10:54] SuperMatt: wassup? [10:55] I just feel like I'm pulling my hair out trying to understand the sdk [10:57] I just want something to allow me to select some files :( [11:00] SuperMatt: the SDK isn't all finished, so there may be gaps in functionality right now. [11:00] SuperMatt: however, hard to know exactly what you want to do without more detail [11:01] SuperMatt: other apps have implemented a directory loading system - such as Beru the ebook reader. [11:01] well, I have my work development day, and I want to write a simple app which will upload a file to an openstack container [11:04] the content-hub is still under work, I don't think we have a file picker/way to pick files for confined apps atm (also note that Ubuntu touch tries to not expose the filesystem/files to users) [11:05] ah right, so trying to do this in the ubuntu sdk might be a little foolhardy right now? [11:15] SuperMatt, right, are you writing an app for "touch" or for desktop? [11:16] desktop [11:16] you might want to use plain qt for that and port your code to the uitk later when it has proper support for e.g picking [11:16] though it'd be nice if it worked for touch at some point [11:16] right, I would say just use plain qt with a fileselector [11:16] ok, sure [11:16] the picker is not ready yet for what you want to do [11:17] you know, for now I'll just make it a little hacky === chriadam is now known as chriadam|away === _salem is now known as salem_ [12:52] popey: looks like someone opened Flashback on the N10 at MWC :) [12:52] popey: I saw a brief glimpse of it in one of the videos showing Rick spencer demoing the tablet [12:55] heh [12:55] yeah, it was on the list of "nice things to demo" [12:55] hehe === salem_ is now known as _salem === om26er is now known as om26er|doc === om26er|doc is now known as om26er [14:50] popey: I'll most likely be late for the reminders hangout. still in a unity meeting [14:51] ok, ping me when you're about === _salem is now known as salem_ [15:26] mzanetti, popey, just arrived at home, I'm lucky that you're late :-) === blaroche_ is now known as blaroche [15:26] popey: I'd be available now. still want to do the meeting? [15:27] rpadovani: heh, perfect timing [15:27] wow :-) [15:27] ok [15:27] lets go [16:11] no N7 for me :) http://developer.ubuntu.com/2014/02/announcing-the-latest-ubuntu-app-showdown-contest/ [16:19] heh daker [16:21] :) [16:32] epic Unicode fail on Planet Ubuntu [16:32] although I don't know whether it's PU's fault or developer.ubuntu.com's RSS feed's fault :) [16:33] aquarius, but you can read this article in english too :) [16:33] ogra, the problem isn't that there's an English one, it's that the Chinese one isn't in Chinese, it's a load of garbled rubbish :) [16:33] pfft [16:33] Looks to me like something somewhere it interpreting utf8 as latin-1 or similar [16:34] chinese is always a load of grabled stuff if you cant read it :P [16:34] it *looks* like Chinese, though, even if I don't understand what it means :) [16:34] though it usually looks better than this i have to admit :) [16:34] I daresay English is garbled if you read Chinese [16:34] aquarius: http://i.imgur.com/zh89at0.png [16:35] daker, the developer.ubuntu.com post is fine [16:35] daker, check Planet Ubuntu [16:35] yep [16:35] OMG! [16:35] planet ios oooold [16:35] *is [16:36] I don't know whether developer.ubuntu.com's RSS feed is wrong (and Planet Ubuntu is correctly displaying the wrongness that it was given), or developer.ubuntu.com is right and Planet Ubuntu doesn't know how to properly handle Unicode ;) [16:36] i think the latter [16:36] its really old software [16:37] that's my guess too, but I don't know :) [16:37] aquarius: http://developer.ubuntu.com/tag/planetubuntu/feed/ [16:37] hm, encoding error on that page [16:37] so maybe d.u.c is wrong after all [16:38] hurray...we can see the ubuntuappshowdown reddit start buzzzing with activity :) [16:38] daker, strangely, the chinese post isn't in that feed? Unless I'm missing something [16:39] nik90, there's a dedicated reddit? [16:39] I should write a showdown app, shouldn't I? [16:39] aquarius: ofcourse there is a dedicated reddit -> http://www.reddit.com/r/ubuntuappshowdown/ [16:39] http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fdeveloper.ubuntu.com%2Ftag%2Fplanetubuntu%2Ffeed%2F moans about some invalid apostrophes, but suggests it's OK [16:39] aquarius: as for the showdown...you are more than welcome to try ;) [16:40] ha! I am already subscribed to it :) [16:40] Am I allowed to enter an app which I started working on before the Showdown, if I only started working on it on Sunday? [16:40] aquarius: you said that just to make me post the reddit link, eh [16:40] aquarius: maybe the tag was removed after the planet synced [16:41] daker, dunno [16:42] who even runs planet? [16:42] IS [16:43] webops ? [16:43] well, the feed *looks* OK to me, in that it correctly shows the line of Chinese characters in the English post. (I assume that it means "read this post in Chinese" or similar.) [16:43] so I think the problem is with planet. [16:44] might wanna nudge a Canonical web team person (who will know about encoding stuff on the web) and an IS person to get together and fix it? === gatox is now known as gatox_lunch [17:14] balloons: ping [17:14] hallo m-b-o [17:14] hallo [17:15] ping elopio, m-b-o is about now as well [17:16] balloons: I've updated the mp! should now worl on phone and tablet BUT I've switched the initial mode back to phone. So I don't know what will happen on tablet (but sandbox run worked) [17:17] m-b-o, I believe you are missing tests for the tablet specific things right? It should run the phone tests fine [17:18] balloons: more or less. there are no really specific tests for tablet mode at the moment [17:18] m-b-o, so ideally the tests wouldhave landed with the features, but I know mwc got in the way of that [17:19] let's file a bug for the missing tests, and move forward with what we have [17:19] balloons: yes. that would be cool. this mp should at least current issues with tests [17:19] right, which is the priority issue for now [17:20] there is some refactoring to do nevertheless, since last week got some things out of order.. :) [17:20] balloons: do you have a n10? [17:21] m-b-o, yes, and soonish I'll have the smaller tablet as well, so if you need help with that let me know [17:22] oh, you can run the tests on n10? :) [17:22] m-b-o, yes, but we focus on the n7 and n4 now [17:23] balloons I'm fine with that [17:23] so, m-b-o everything is pushed to the MP, it's ready to land? [17:23] yes! [17:24] ok, my phone is currently flashing, hah [17:24] balloons: wait! [17:24] elopio, did you review the mp yyet? [17:25] balloons: fixing the tests is high priority right now? I'm waiting on feedback from dpm, so perhaps we could wait with the top approve. [17:26] m-b-o, need to give it a good review, no reason not to start now. I'm not top approving till we've finished. dpm is @ mwc, so it will be tough to hear from him [17:26] popey ^ ^ should we wait for feedback before switching weather back to phone mode as default? [17:26] what feedback did you need? [17:27] balloons: if it's ok to switch back to phone mode as default [17:28] balloons but it should be ok [17:28] m-b-o, yes, we wanted those changes for mwc, so it's ok to rollback them until you make the changes to do it better [17:28] I mean they were temporary so ;-) [17:29] balloons: yes, think so too. [17:41] balloons: not yet. [17:41] I'll do it now, before I get distracted. [17:58] balloons, m-b-o, I don't like some of the things on the tests, but they need a bigger clean up. [17:58] for example, this is not how we should wait for things to appear on the screen: [17:58] self.assertThat(lambda: self.main_window.select_many('Label',objectName='DayDateLabel'), Eventually(Not(Is(None)), timeout=60)) [17:59] we need to find a loading image, or something like that. The thing that tells the user that we are loading or he has to wait for something. [17:59] but it does seem like an improvement, and if tests still pass, it's ok for me. === gatox_lunch is now known as gatox [18:01] about the qml changes, I don't understand them, so I'm not a good reviewer for that part. [18:06] elopio: that's okay, the qml changes should not break anything. Yes, some parts of the tests are outdated now. They should get refactored (and with some DRY in mind too) [18:06] m-b-o: do you have time next week so we get together and clean the tests a little? [18:06] elopio: yes. which TZ you are in? [18:07] m-b-o: I'm -6, but my schedule is flexible. I'll ping you on monday. [18:07] ok, I'll run a few times through on my device, which is finally finished flashing [18:09] elopio: alright! I'm +1, so we should consider an evening on my side [18:09] m-b-o: ok, thanks. [18:11] elopio: in fact only tuesday or thursday/friday would be possible. ping me on monday, how it's possible for you [18:11] m-b-o: sure. We can also do some of it asynchronously. I'll try to make a small initial branch for you to review on monday. [18:12] elopio: cool, thanks! [18:12] m-b-o, so before I approve, do we have the bug filed for missing tablet tests? [18:13] balloons: nope [18:15] mhall119, I think I don't agree with your "it's all one Ubuntu" post. It *will* be, but it isn't, yet :) [18:17] aquarius: what? you disagree with me on something? I'm shocked! [18:17] * aquarius grins [18:18] mhall119, I thought I'd talk to you about it rather than writing a post, although I like the idea of detailed conversations happening on the Planet (as per discussion last month about how it should have interesting content) [18:18] aquarius: do it on planet [18:19] mhall119, fair enough :) [18:22] m-b-o, got a couple failures still.. interesting [18:24] balloons: hmm, can you send me the logs? I'll be away for a hour [18:25] m-b-o, sure thing.. re-running several more times and seeing whats up [18:53] balloons, ping [18:53] * balloons rattles brai [18:53] *brain [18:53] balloons, hehe i was just looking into ur cmake suggestion... [18:53] balloons, http://bazaar.launchpad.net/~andrew-hayzen/music-app/cmake-simplify/revision/360 [18:53] balloons, am i right in thinking that we won't need this line install(FILES ${MAIN_QML} ${ICON_FILE} DESTINATION ${DATA_DIR}) [18:54] ahayzen, yes [18:54] balloons, will the icon be added from *.png even though it is in images/ [18:54] balloons, as in does it search through the sub-dirs as well? [18:54] you might need to do a bit more work on that [18:55] m-b-o, http://paste.ubuntu.com/7001284/ [18:58] balloons, ok i'll have a play about with it :) ... and the other thing u said u thought u may have seen tht autopilot issue before? on https://code.launchpad.net/~andrew-hayzen/music-app/mediaplayer-simplify/+merge/201265 [19:01] ahayzen, https://code.launchpad.net/~veebers/autopilot-qt/reintroduce-exporting-qobject-children-of-qml-items/+merge/207581 is being worked today.. so hopefully will land soon ;-) [19:04] balloons, awesome so we wait until tht lands then retest :) ...once it is displayed as merged does tht mean we would expect Jenkins to have it? [19:04] ahayzen, pretty close to that [19:04] balloons, cool [19:10] balloons, this appears to create the same click package as before https://code.launchpad.net/~andrew-hayzen/music-app/cmake-simplify/+merge/208457 [19:15] balloons, can u see the click tht jenkins builds? [19:17] ahayzen, we can have it build a click, but we can build one easily locally too [19:18] balloons, cool i built it locally and compared to trunk, the only difference i could see is the new one had the addition of plugins.json [19:18] try installing on the device.. if it has an icon we're good [19:19] balloons, tht was weird cause one which i thought didn't have it did...maybe a restart to be safe === bfiller is now known as bfiller_afk [19:27] elopio, nik90 I get errors run the AP tests for clock in trunk -- is it just me? [19:28] balloons: which tests? and also on device or desktop? [19:28] nik90, on my mako, test_add_single_type_alarm_must_add_to_alarm_list and test_delete_alarm_must_delete_from_alarm_list [19:29] for instance, File "/home/phablet/autopilot/ubuntu_clock_app/emulators.py", line 250, in delete_alarm [19:29] self.drag_page_up('AlarmPage') [19:29] TypeError: drag_page_up() takes exactly 1 argument (2 given) [19:29] sorry for the big paste.. I'll give a full log, but this are trivial issues [19:30] balloons: hmm I can imagine why it gives an error [19:30] balloons: right, I messed there. [19:31] balloons: let me get a fix asap.. [19:31] balloons: I am almost done with my stopwatch AP test cleanup [19:31] nik90, elopio why did we land this? [19:31] balloons: I am not sure why jenkins didn't flag this [19:31] nik90: lines 250 and 261. [19:31] no worries on the error, I'm just confused why we landed it broken [19:31] sorry about that. [19:31] I want to make sure I've got the right stuff, etc :-) [19:32] balloons, nik90: The thing is that on desktop, the qmlscene window is of the size it was last opened [19:32] balloons: I missed that during my code review [19:32] elopio: ah yes [19:32] so sometimes you get to run only the tests in !wideAspect mode. [19:32] ahh.. ok, gotha [19:32] elopio: that's why it didn't fail for me [19:32] elopio: I will take care of fixing them [19:32] no worries then.. so yea, there's a few errors. I'll do another full run and send the log [19:33] balloons: sure [19:33] nik90, balloons: I'm trying to simulate the window size with some helpers from the toolkit. I can set now the grid unit px, but I'm still missing a nice way to resize the qmlscene window. [19:33] ty :-) [19:33] elopio, oO [19:33] elopio: ooh nice [19:33] https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/device_emulation_scenarios/+merge/208146 [19:34] I think I won't be able to finish this week. [19:34] elopio: btw I noticed that your lp:~elopio/ubuntu-ui-toolkit/listview-scroll_to_bottom has been approved and ready to land [19:34] elopio: is that the one which allows us to choose which list item to click? [19:35] nik90: yes! :D [19:35] nik90: no :( [19:35] elopio, I'm a bit sad we didn't talk emulator @ the sprint now [19:35] nik90: I'm currently fixing this: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1275060 [19:35] Launchpad bug 1275060 in Ubuntu UI Toolkit "QQuickListView fails to click an element if part of the list is out of view" [Undecided,Confirmed] [19:35] that's the one that will let us choose items from the list. But the other one was a prerequisite. [19:35] elopio: ah ... well atleast that bug is unblocked now since your rate merge to AP has been merged [19:36] elopio: no worries, even if it landed I wouldn't be able to use them since I am on saucy... [19:36] elopio: will upgrade asap to trusty [19:37] I'm totally unblocked now. I just wish I had another pair of hands :) [19:37] hehe [19:37] tell me about it [19:37] balloons: I also started working on the rss. If you see carla before me, please tell her to ping me. [19:38] elopio: one last question before I continue with my work [19:39] elopio: in order to test deleting laps, I need to first start stopwatch -> create lap -> delete lap [19:39] elopio, sure thing [19:39] elopio: should start stopwatch and create lap be part of the emulator function delete_lap() ? [19:39] balloons: ur input as well ^^ [19:39] nik90: no, we should try to have a line on the test for each action that the user does. [19:40] something like [19:41] test(self): [19:41] stop_watch = self.main_view.go_to_stop_watch() [19:41] stop_watch.start() [19:41] stop_watch.create_lap() [19:41] stop_watch.delete_lap() [19:41] self.assert_that_lap_was_deleted() [19:41] ah ok [19:42] you can complement that with another couple of tests that would be: [19:42] test(self): [19:42] stop_watch = self.main_view.go_to_stop_watch() [19:42] stop_watch.start() [19:42] self.assert_that_stop_watch_was_started() [19:42] and test(self): [19:42] stop_watch = self.main_view.go_to_stop_watch() [19:42] stop_watch.start() [19:42] stop_watch.create_lap() [19:42] self.assert_that_lap_was_created() [19:42] elopio, nik90 here's one of the logs from a run http://paste.ubuntu.com/7001509/ [19:43] elopio: those complimentary tests are already done :) [19:43] balloons: thanks. I think I can reproduce the errors on desktop. Will ping you tomorrow so we can repeat this exercise once again! :) [19:44] balloons: the drag errors are all because I made that stupid mistake. The last one is weird. [19:44] m-b-o, :-) Have a good night sir [19:44] it's as if your days dialog was closed while trying to select a day. [19:44] elopio, I can run the test and watch if you have questions [19:44] balloons thanks ! [19:45] back in a bit; food beckons [19:48] balloons: yes, please. try to run only that last one and see if you find something weird. [19:56] elopio: stopwatch AP done :) just need to add the necessary drag_page_up functions... going for dinner.. when I get back I will do it and then propose a MP. [19:56] nik90: thanks! [19:56] buen provecho. [20:15] elopio, another full run: http://paste.ubuntu.com/7001644/ [20:25] rpadovani, ping [20:57] elopio, balloons: https://code.launchpad.net/~nik90/ubuntu-clock-app/reorganise-stopwatch-tests/+merge/208475 [21:08] elopio, balloons: fixed the alarm drag issue at https://code.launchpad.net/~nik90/ubuntu-clock-app/fix-alarm-drag-test/+merge/208477 [21:21] * nik90 hugs mzanetti for his expandable list element being approved. [21:21] mzanetti: Looking forward to using it in my personal app :) [21:26] elopio: can you top approve again? looks like a random failure [21:28] nik90: I'll re-run it just to be extra safe. [21:28] elopio: ok [21:31] nik90: this is the same error we are seeing in jenkins. [21:31] it seems we get an old_saved_city_count = 0 [21:31] maybe because we are not waiting enough, [21:31] elopio: hmm..it passed for me [21:31] but you will be refactoring the clock tests, right? [21:33] elopio: but yes I will be targetting the clock tests next [21:33] nik90: yes, it doesn't happens always. [21:33] elopio: once the stopwatch tests are merged [21:37] I still can't run it here :( But almost everything is crashing here, I'll make a reinstall in the night. [21:37] nik90: should I leave you my comments on the branch, or would you like to discuss them here? [21:37] elopio: comments is better since it is more permanent and I won't lose them [21:37] nik90: ack. [21:37] elopio: reinstalling trusty or the emulator/ [21:37] ? [21:37] reinstalling trusty. I'll even remove my home this time, and from now on I'll use virtual machines when testing something risky. I've learned my lesson. [21:42] balloons, elopio: the tests passed on the emulator beautifully! I had only 1 failure which was the delete alarm test [21:42] it did take a long time though [21:45] nik90: I don't understand the Record lap icon. What does it mean? [21:45] elopio: record lap icon? [21:45] elopio: one is a reset icon and the other is a create lap icon [21:45] nik90: yes, on the stopwatch, there's one to reset, and the other [21:46] it's like a clock half full? [21:46] elopio: yeah sort of...half full clock where you press the lap [21:47] given by designers [21:47] I will check if they can improve its appearance for better clarity [21:47] I don't get it, but it might be just me :) [21:49] nik90: btw, I think I commented about this on g+, but I love what you did to differentiate the alarm, the timer and the stopwatch. [21:49] it's so cool how a couple of lines can improve things this much. [21:49] elopio: ah thnx :) .. it was all the work of Lucas (our community designer) [22:02] nik90: your refactor makes things a lot better. I left you some more comments, just because I'm a pain in the ass. [22:02] elopio: lol [22:02] you already did the important part. The rest are just small things that we can improve. [22:03] balloons, pong, sorry for the late [22:04] elopio: I will fix those comments [22:05] nik90: thanks. I'm reading the test cases now. The following comments are more for discussion, feel free to not implement them if you don't want to. === seb128_ is now known as seb128 [22:32] rpadovani, no worries, it must be way late now.. but if you can leave me a comment about how to run reminders.qml via qmlscene on the command line that would be great [22:33] rpadovani, running qmlscene reminders.qml doesn't work === salem_ is now known as _salem [23:24] elopio: fixed the stuff you mentioned in the comments [23:24] balloons: the alarm fix is in trunk btw [23:24] nik90: thanks. I'll take a look. [23:25] nik90, elopio are we set now? [23:25] I mean for a store release :-) [23:25] balloons: is it urgent? [23:25] nik90, no, the goal was to push a version to the store that has tests passing [23:26] balloons: ah okay [23:26] balloons: the reason I ask is that I am going to clean up the clock tests as well similar to alarms, stopwatch and timer. [23:26] balloons: however I will only propose it tomorrow since it is late now [23:27] nik90: I forgot to click send on my review of the tests :) [23:27] elopio: you mean more comments? [23:28] nik90: yes, a couple. I'm sorry, I feel bad about you, I'm a mean reviewer. [23:28] elopio: bring it on..it is fun fixing them [23:28] nik90: the changes you did are prefect, thank you very much. [23:29] nik90: oh, it's great you are having fun :) [23:29] when we are done with the helpers refactors, we should discuss about failing with a meaningful error message. [23:30] I need to think about it, and your input will be great. [23:30] elopio: sure...that would be nice since the error message at the moment are terrible [23:31] I would like more user friendly error messages :) [23:36] popey: ping [23:39] mhall119: PM ? [23:40] sure [23:42] elopio: without the eventually statement the test fails === bfiller is now known as bfiller_afk [23:56] nik90: hum, so we need it. [23:57] elopio: yup, also the test passes without the sleep() [23:57] I didn't understood why, I'll check again [23:58] nik90: yes, without the sleep it passes. But lets say that the stop button is not working, and those two statements run insanely fast, in less than one millisecond. [23:58] then your test would still pass. [23:58] ah [23:58] if we sleep a second, they won't be able to run in less than one millisecond. [23:58] maybe that needs a comment. [23:59] hum, I still don't get why the eventually is needed there.