=== nik90_ is now known as nik90 | ||
thomi | veebers: hey man, I'm back | 02:12 |
---|---|---|
thomi | veebers: any luck on the release jobs? | 02:12 |
veebers | thomi: hey I can see that something odd happened with this one: http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/122/label=daily-mako/testReport/mediaplayer_app.tests.test_player_with_video/TestPlayerWithVideo/test_scene_selector_operation_with_touch_/ | 02:13 |
veebers | apparently, WireProtocolVersionMismatch but the stack trace is coming from python2.7 | 02:13 |
thomi | the WPVM error is actually a red herring in this case | 02:13 |
thomi | AP assumes that if any DBusException happened during the GetVersion()call, that the version is 1.2 | 02:14 |
veebers | I see we get a failure for 'ubuntu_filemanager_app.phablet-test-run' in both, so something is happening here | 02:14 |
veebers | right | 02:14 |
veebers | I suspect that app has been renamed | 02:14 |
thomi | which app? | 02:15 |
veebers | ubuntu_filemanager | 02:15 |
thomi | what makes you think that? | 02:15 |
veebers | I think renamed to filemanager | 02:15 |
veebers | looking at the smokeeng dash | 02:15 |
veebers | last time we consistently had that error was when the rss reader was renamed too | 02:15 |
thomi | hmm, odd that the tests still exist for the old version then | 02:15 |
veebers | where are you seeing the old version tests? | 02:16 |
thomi | well, ubuntu_filemanager_app | 02:16 |
veebers | I think phablet-setup-tests may only pull in filemanager or something similar | 02:17 |
thomi | hmm, well, we're running the tests for something called ubuntu_filemanager_app - do you think that's incorrect? | 02:17 |
veebers | thomi: yeah, I think the job needs updating (i.e. the list of tests to run) | 02:18 |
veebers | It should be changed so that it pulls the list of test names from the tool that generates it | 02:19 |
veebers | From memory there is a way to get a list of test suites | 02:19 |
veebers | we should be using that not the hardcoded list | 02:19 |
thomi | ok. what I'm saying is that it's odd that those tests pass, if the app has been renamed. Totally agree that we shouldn't need to fuck about like this though :) | 02:20 |
veebers | thomi: where are you seeing the tests pass? I'm seeing a total failure with no tests run | 02:21 |
veebers | hence why this 'ubuntu_filemanager_app.phablet-test-run ' is in the failures and not a list of ubuntu_filemanager_app tests | 02:21 |
thomi | ah wait, I see now | 02:21 |
thomi | sorry | 02:21 |
thomi | I was reading the log wrong | 02:21 |
veebers | ah makes sense now | 02:22 |
veebers | I'll follow up with andy and see if we can't make that job smarter in that regard | 02:22 |
veebers | moving on to the ubuntu_clock_app, the same 5 failures appear in the smokeeng and both gatekeeper jobs | 02:23 |
veebers | so it looks like there are issue there outside of a newer AP | 02:23 |
veebers | (I'm just confirming/comparing the smokeeng run with 1.5) | 02:23 |
veebers | thomi: oh that latest AP video of yours is F-ing awesome! well done :-) | 02:25 |
thomi | heh, you think it works? | 02:25 |
thomi | it's really hard to get the 'art' and the voice track lined up | 02:25 |
thomi | also, there's an IRC pop up from you that appears at one stage :) | 02:26 |
thomi | so you're on youtube now :) | 02:26 |
thomi | it's nothing embarrasing though :( | 02:26 |
veebers | thomi: hah I wondered who the popup was from :-) | 02:26 |
thomi | if you watch it in HD you can see it quite clearly | 02:26 |
veebers | If I could make a suggestion, it would be to somehow have the brushes etc. on hot-keys so the cursor isn't jumping around the screen and removing the color picker side bar | 02:27 |
veebers | thomi: odd, i tried that but it stayed blurry for me :-P | 02:27 |
thomi | yeah, that's going to be my next trick - do it all in fullscreen mode | 02:27 |
veebers | nice | 02:27 |
veebers | the handwriting has improved quite nicely ;-) | 02:28 |
thomi | heh | 02:28 |
thomi | the trick is confidence. confidence, and many, many, many takes | 02:28 |
veebers | heh :-) Well it worked out really well. You should link to the latest video in the channels topic too | 02:29 |
=== thomi changed the topic of #ubuntu-autopilot to: Autopilot documentation is at http://developer.ubuntu.com/api/devel/ubuntu-14.04/autopilot/ | latest tutorial video is: https://www.youtube.com/watch?v=En1MaDDp9_8 | ||
veebers | ^_^ | 02:31 |
veebers | thomi: so you know who I would ask about some minor improvements to the smokeng dash? Is that something we do and propose or is someone looking after it? | 02:35 |
thomi | I don't really know. I guess we'd talk about what you want first, whip up a quick feature spec... TBH be honest we're most likely going to be the ones to do it I guess | 02:36 |
thomi | which is ok, as long as we can get it merged | 02:36 |
veebers | thomi: aight, it should be pretty simple. I just wanted the test suite added to the title, makes it easy to scroll through many tabs that way | 02:37 |
veebers | thomi: unless you have any objections I'll fire off the gateway keeper again with those suites we saw fail (changing ubuntu_filemanager_app -> filemanager) | 02:43 |
veebers | thomi: I take that there is no objections? :-) | 02:54 |
thomi | hmm? | 02:55 |
thomi | go for it | 02:55 |
thomi | veebers: did you see http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/124/ ? | 04:20 |
veebers | thomi: Not recently I'll look now | 04:20 |
veebers | hmm, has a couple more errors thanks to filemanager. Is also a different image ver from run 122 (18:20140509:20140506.1 vs 21:20140510.1:20140506.1) | 04:24 |
thomi | veebers: that wasn't a full run, right? | 04:24 |
veebers | thomi: the most recent? No, was just the suites that appeared in the fail list from run 122 (with renamed filemanager) | 04:24 |
thomi | hmmm | 04:26 |
thomi | not really sure what to do - suggestions? | 04:26 |
* veebers ponders | 04:32 | |
veebers | thomi: perhaps an email to the devs or ubuntu-phone stating 'These are the errors/fails we have. x is considered faulty tests (as per failures in smokeeng) the others are either new or faulty too' | 04:34 |
veebers | and put the effort onto the devs to ensure the tests are correct | 04:34 |
thomi | hmmmm - the run without our PPA had similar failures - do those failures show up on the CI dashboard? | 04:38 |
veebers | That's what I mentioned earlier on (comparison of smokeeng to failures.) the clock app matches failures in both our run and smokeeng dash | 04:39 |
veebers | I'm just checking the weather app now actually as it lookslike the match up | 04:40 |
veebers | The weather app failures match up with the smokeeng failures, just double checking the clock failures but suspect the same thing | 04:43 |
veebers | thomi: same thing with the clock app except we have an extra failure 'test_toggle_alarm_status_must_enable_or_disable_alarm'. | 04:46 |
thomi | is it consistent? Maybe we should re-run the clock-app tests? | 04:47 |
veebers | thomi: consistent? you mean between runs of the gatekeeper? I'll have to check again. I just compared the latest gatekeeper against the latest smokeeng | 04:49 |
veebers | thomi: Perhaps we should re-run clock and weather to make sure it is consistent though | 04:49 |
thomi | yeah | 04:50 |
thomi | can you kick it off please? | 04:50 |
veebers | sure ting | 04:52 |
veebers | done | 04:53 |
=== vrruiz_ is now known as rvr | ||
tscheck | Hello. | 12:42 |
tscheck | I'm struggling with the vis tool on the 14.04 release using the qt4testapp from the libautopilot_qt unit tests. I don't see QDeclarativeItem. Is this a know issue? | 13:23 |
tscheck | export QT_SELECT=qt4 | 13:24 |
tscheck | /usr/share/libautopilot-qt/qt4testapp -testability /usr/share/libautopilot-qt/qt4.qml & | 13:24 |
tscheck | autopilot vis | 13:24 |
tscheck | When I run a simple test case with a print_tree() and a sleep, vis shows the element. | 13:25 |
cgoldberg | tscheck, hey.. you can file a bug and it will get triaged... there has been some recent work on vis tests | 14:13 |
cgoldberg | tscheck, https://bugs.launchpad.net/autopilot-qt/+filebug | 14:14 |
balloons | elopio, you about? Got a couiple ?'s for you. how's reminders tests looking? And I believe you and team work on SDK testing; would EDS fall under that; at least the extensions we have for alarms and things? | 14:39 |
elopio | balloons: all tests just passed | 14:39 |
elopio | https://code.launchpad.net/~elopio/reminders-app/test_with_account/+merge/218688 | 14:39 |
elopio | can you merge it? | 14:39 |
balloons | ohh yes I kicked it off again :-) | 14:40 |
balloons | it answered my question, hah | 14:40 |
balloons | merging now | 14:40 |
elopio | balloons: and about eds, ChrisGagnon is working on enabling all the tests for the qt components. | 14:41 |
elopio | I'm not sure how well tested is eds already. | 14:41 |
elopio | balloons: take a look at the last slide: https://docs.google.com/a/canonical.com/presentation/d/14Jpe7UDo-emqLgSFii5uPF-fPy0BoAQTX1kMfwU5AnI/edit#slide=id.g3381b7c66_1126 | 14:42 |
elopio | we should talk to him to see if he has eds in the roadmap. | 14:43 |
balloons | elopio, but we have custom work on it right? I mean the issues we see are with our addon components which we ship with the sdk. Right? | 14:45 |
balloons | ty for letting me know to talk to Chris ;- | 14:45 |
elopio | balloons: yes, if the work is on our branches, we should have tests for it. If it's on someone else's branches, we should contribute tests there. | 14:46 |
tscheck | @cgoldberg: Ok. I will file it. | 14:46 |
elopio | one other important thing we discussed with the sdk team is about code coverage. | 14:46 |
elopio | we don't really know where we are missing tests. | 14:46 |
balloons | elopio, so I think it | 14:51 |
balloons | so it's 2 pronged. I should make sure Chris is getting upstream tests going for it, and I guess make sure it's on your team's radar to add it to the sdk testsuite? | 14:52 |
elopio | balloons: it's a thin line between chris and me there. So probably we should all talk about it to see who takes care of what. | 14:54 |
elopio | I'm going to take a look at the eds components that we add. | 14:54 |
balloons | elopio, awesome. It's something I'd like to get on the schedule for Malta as it's a constant regressor for my team (core apps). | 14:55 |
elopio | balloons: ok, please reply to julien's email about call for topics, so we have it on schedule. | 14:56 |
balloons | elopio, yep will do. Just wanted to see if it was on someone's radar or not, and if work had been done | 14:56 |
balloons | no worries and thank you! | 14:56 |
=== fginther is now known as fginther|lunch | ||
=== fginther|lunch is now known as fginther | ||
thomi | morning | 20:09 |
veebers | morning | 20:36 |
thomi | barry: who should I talk to if I want to convince someone to package the 'youtube' sphinx third party plugin from https://bitbucket.org/birkenfeld/sphinx-contrib/src/940757f22e335f6ae98521621201683d6bab1d60/youtube/?at=default ? We already package opther plugins from the same repo, just not that one | 20:57 |
barry | thomi: is it on pypi? i'd help sponsor it into debian if you package it up :) | 21:02 |
thomi | the packaging is the hard part - I've never done it for something that I'm not the upstream for | 21:04 |
barry | thomi: it's *probably* easy: https://wiki.debian.org/Python/LibraryStyleGuide | 21:05 |
thomi | barry: when is your EOD? | 21:05 |
barry | thomi: at least another hour away | 21:05 |
thomi | barry: cool - will let you know | 21:10 |
thomi | barry: ugh, won't get to it today it looks like - will send you an email overnight :) | 21:36 |
barry | :) | 21:36 |
thomi | barry: so, do I make a debioan/ dir in a checkout of the upstream source? | 22:00 |
thomi | barry: or in a completely seaprate branch? | 22:00 |
barry | thomi: | 22:19 |
barry | thomi: i've found it easiest when package something brand new, to create the debian/ inside an unpacked upstream tarball. once you have a package that builds and looks good, then you can take the .dsc and import/inject that into the vcs of your choice. that's assuming you'll want to maintain it in debian, which i suggest (i.e. it's not ubuntu specific) | 22:21 |
thomi | barry: OK, I'll do my best, and you can tell me where I've stuffed it up tomorrow. | 22:28 |
thomi | right now I need moar coffee | 22:28 |
barry | :) | 22:28 |
veebers | thomi: we may have an issue with filemanager and ppa autopilot. I'm rerunning the gatekeeper without the ppa and just filemanager so we can compare results on the same hardware etc. | 22:44 |
thomi | veebers: ok - keep me posted please :) | 22:47 |
veebers | thomi: can do | 22:47 |
barry | thomi: what's the eta for the final uploads to eradicate py2 from touch? | 23:49 |
thomi | hey barry - just emailed you, assumed you'd EOD'd already :) | 23:49 |
thomi | barry: we're landing the AP parts now | 23:49 |
thomi | just doing the final checks (how's that going veebers?) | 23:49 |
barry | thomi: i was, but i couldn't resist seeing how a build was going :) | 23:49 |
thomi | barry: I'd expect the autopilot package to land today | 23:49 |
veebers | thomi: re-running the job as something failed | 23:49 |
veebers | (see #ci) | 23:50 |
thomi | veebers: that's not finished yet? oh, you mean, re-re running :) | 23:50 |
veebers | ack :-) | 23:50 |
thomi | boooo | 23:50 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!