#ubuntu-autopilot 2015-03-02
<veebers> thomi: hey, you have a moment?
<thomi> veebers: depends
<veebers> thomi: heh, was just going to ask, what do you know about NotImplemented? I thought it was a 'normal' exception, but it's not a callable (like ValueError for instance)
<thomi> veebers: NotImplementedError is the callable
<veebers> thomi: ugh, of course, thanks :-)
#ubuntu-autopilot 2015-03-03
<thomi> barry: got a second?
<barry> thomi: about to head to a meeting in 4m
<thomi> barry: this should be fast... I'm building a deb package, and quilt is complaining about upstream source changes, but I haven't made any, and the diff it's generating (to show me the changes I made) is  http://paste.ubuntu.com/10518520/
<thomi> it thinks I modified /dev/null? wtf?
<thomi> oh, or is that it's way of saying that I created an empty file?
<barry> thomi: the latter :)
<barry> thomi: maybe the test suite leaves a turd?
 * thomi rolls eyes
<thomi> yeah
<thomi> thanks :D
<thomi> thomas
<thomi> oops
<barry> thomi: np! :)
#ubuntu-autopilot 2015-03-04
<thomi> barry: I don't suppose you're still around?
#ubuntu-autopilot 2015-03-12
<balloons> thomi, still plan to update gitg in vivid? I'm confused because it seems like a big sync to 3.14 happened, and it is in vivid
<balloons> I do agree on gitg though, I too found it the best and used it
<balloons> not tried the new version :-)
<thomi> balloons: yeah, I think it got synced for vivid alreday
#ubuntu-autopilot 2015-03-14
<nik90> balloons: I suspect autopilot hates me :P .. I tried running the clock app AP tests on a fresh vivid install and I get the following error http://paste.ubuntu.com/10596507/
<daz_> anyone available to help?
<daz_> got it
#ubuntu-autopilot 2015-03-15
<rpadovani> balloons, o/ when you've time, could you please take a look to http://523-777-4502:8080/job/generic-mediumtests-utopic/2341/? ?
#ubuntu-autopilot 2015-03-16
<nik90> balloons: hey, can you ping me later when you are free..I am having trouble running clock app autopilot tests on my vivid laptop (log http://paste.ubuntu.com/10596507/ )
<balloons> ohh theres a queue in here :-)
<balloons> morning all!
<balloons> rpadovani, I re-ran it. It returned nothing to jenkins so it's hard to say what went wrong
<rpadovani> ty!
<balloons> nik90, so this log.. how do you generate it?
<balloons> ohh is this a fresh checkout? if it's on the desktop, it's not finding the binary
<balloons> we should put the python in to find the binary rather than require it be in a specific location.. there's a cmake parser, which does work to do this
<nik90> balloons: yeah is on a fresh vivid install on the desktop
<nik90> what do you mean put python in to find the binary?
<balloons> nik90, heh, I'm rambling aloud. Ok, so to fix your issue make sure you build as instructed in the README. Unless someone has changed something the tests expect the binary in that specific folder
<balloons> there is some python code we can add to the testsuite that would read the cmake build file instead of requiring a specific folder for the binary. So during test startup, it reads the cmake build file and looks for the binary that way, instead of requiring a fixed relative path
<nik90> balloons: omg, I am an idiot, I forgot to build the binary...(QtC usually does that for me)
<balloons> nik90, right :-) not building it also causes that, heh
<nik90> balloons: so after building the binary, and runnig autopilot run test_name works... however i tried using autopilot3 but it fails and complains something about  DisplayConnectionError http://paste.ubuntu.com/10609916/
<nik90> I figured if I could use autopilot3 it would help me use autopilot3-sandbox-run and the other cool features
<nik90> I see the clock app show up and then get closed almost immediately while using autopilot3
<balloons> nik90, autopilot3 causes you problems.. interesting
<balloons> trusty ofc, and what version of autopilot3?
<nik90> balloons: no no this is on vivid
<balloons> oh nice
<nik90> balloons: version info http://paste.ubuntu.com/10609963/
<balloons> just your normal desktop?
<nik90> yup
<nik90> (my old laptop)
<nik90> running vivid daily build 1386
<balloons> well I guess let me try as well locally here. However, autopilot2 works fine for you
<balloons> ot
<nik90> yeah autopilot works fine, so I guess I can use it for now
<balloons> I can't imagine the backend code is substantially different, but we can look
<nik90> I have been asked to improve the clock app's AP status..so I will be adding back the functional tests for editing alarms, etc that currently only exist in the QML test suite
<balloons> nik90, ohh.. what's clock look like on the dashboard anyway?
<nik90> balloons: every AP test fails :/ due to the location prompt
<nik90> so I cannot release a new click to the store as a resutl
<balloons> nik90, ahh well I guess we should start by fixing that eh?
<nik90> balloons: I can't since it requires upstream helpers to be added in the trust-store, let me grab the MP we have currently that requires upstream fix
<balloons> and there is nothing wrong with keeping your AP test suite smaller.
<balloons> nik90, we can bundle the helpers locally for now and transition later
<nik90> https://code.launchpad.net/~brendan-donegan/ubuntu-clock-app/disable_location_prompt/+merge/242682
<nik90> check out the last reply from iahmad
<balloons> nik90, right so that's all landed.. it means we can write helpers now and bundle them locally. And ofc upstream them and transition after
<balloons> make sense?
<nik90> yes
<balloons> nik90, I get the same error as you, nice
<nik90> ooh :P
<balloons> and indeed, autopilot works..investigation and bug filing time
<nik90> balloons: just for clock app? Since otherwise this might have been spotted earlier on
<balloons> nik90, no it's for everything.. Something must have broken it recently
<balloons> I have a small update I can do so I'm doing that first
<balloons> are you fully up to date?
<nik90> yeah I am fully up to date
<balloons> yea nothing in here will change anything so I suspected as much
<balloons> let me try and pinpoint what broke it
<balloons> rpadovani, looks like you got a valid run that time: http://523-777-4502:8080/job/generic-mediumtests-utopic/2357/testReport/junit/ubuntu_calculator_app.tests.test_main/MainTestCase/test_sin/
<balloons> at least a log
<balloons> nik90, so carry on with autopilot2 for now.. This should be fun to track down for someone else :-)
<nik90> balloons: yes, I have started writing some new tests. I haven't had any success with running AP tests on the phone (using all the methods that I could find), so the location-prompt thing will have to wait for now.
<paulliu> hi. If I add some cout/cerr in platform-api. How do I print those out when using autopilot3?
<balloons> nik90, you don't have a spare phone just for testing do you?
<nik90> balloons: I use my S4 Android as my primary phone, and the N4 just for testing and developing for UT. I tried the script popey and also adt-run on devel-proposed as well
<balloons> nik90, right. I was going to say grabbing devel-proposed image with vivid should let you use adt easily enough. It should just work
<balloons> alternatively you can grab devel-proposed, make it r/w and install autopilot packages again. Then copy the tests and run them just like you do on the desktop. The downside of that is you'll have to occassionally re-flash the phone to update it
<nik90> balloons: For instance, when I tried adt-run on the music app AP tests, they all didnt get past the welcome wizard. I am not sure why.
<nik90> hmm ok I will do that
<balloons> nik90, if you are interested in cloning what happens on the dashboard, this is how CI does it. Essentially they do what I said as the latter option: http://ubuntu-test-cases-touch.readthedocs.org/en/latest/
<balloons> so if you do that, you may as well simply use there script
<balloons> nik90, if they didn't get past the welcome wizard that might just be an issue with the tests.
<nik90> ok
<nik90> balloons: wow that docs looks detailed and easy to follow, thnx. I will give that a go
 * ahayzen hides and pretends the tests are working perfectly :)
<nik90> ahayzen: lol
<nik90> ahayzen: I just took another app to see if something was wrong with my testing environment
<ahayzen> haha
<balloons> nik90, good let me know.. CI is actively documenting that atm, I've been wanting to make sure it's actually usable by someone like yourself
<nik90> will do
#ubuntu-autopilot 2015-03-17
<elopio> ping MacSlow: I'm trying to build your branch but I get:
<elopio> http://paste.ubuntu.com/10615701/
<MacSlow> elopio, *sigh* I forgot to list some of the build-dependencies for that branch...
<MacSlow> elopio, I'll send you the missing bits...
<MacSlow> elopio, missing build-dep sent via eMail
<balloons> nik90, any luck with the CI doc?
<nik90> balloons: I didn't have time to try it out yesterday. Will let you know how it goes by the end of todau
<nik90> s/todau/today
<balloons> nik90, thanks, no rush, just curious
<elopio> thanks MacSlow. I'll try again after my current meeting.
<MacSlow> elopio, ok
<nik90> balloons: Hey, I went through the CI docs and ran the scripts as per the instructions. I finally could see clock app running on the device :-)
<nik90> balloons: *however* after the ap tests were run, the test-results.xml file does not show any of the test results. So I cannot test what passed and what failed
<nik90> balloons: this is what the xml file shows https://i.imgur.com/eYwx6Qn.png
<cgoldberg> sup amigos  0/
<balloons> nik90, nice.. well, heh not nice
<nik90> balloons: I haven't looked into the subunit file yet as I need to install trv viewer first
<nik90> balloons: is there a place where I can file bugs about the docs?
<nik90> I noticed that the welcome wizard was not disabled as it should have been and a few others
<veebers> hey cgoldberg o/ Hows things?
<cgoldberg> hey veebers!  I'm really good, thanks.  hows you?
<veebers> cgoldberg: good thanks man :-)
<cgoldberg> veebers, have you seen the new Das Keyboard 4?  I want one.
<nik90> balloons: the subunit files shows the results correctly though :) https://imgur.com/BNyUBbg
<nik90> thomi: ^^ your trv viewer https://imgur.com/BNyUBbg
<cgoldberg> @veebers: http://www.daskeyboard.com/daskeyboard-4-professional/
<thomi> hey nik90 - that's nothing to do with me anymore :D
<thomi> oh hey cgoldberg, what's up?
<cgoldberg> hey thomi 0/
<nik90> thomi: oh....Just noticed that the trv youtube video I saw was dated august 2014 ;P
<thomi> nik90: yeah - I might hack on it some more if I get time
<veebers> cgoldberg: heh, no I haven't seen it yet. I picked up a Poker 2 recently. That should tide me over for a while :-)
<cgoldberg> veebers, do you touch-type?  the blank keycaps you can get it with are totally johncrosby@example.net... but I need lettering on my caps :(
<veebers> cgoldberg: I 90% touch type :-) The change-up with the new 60% layout mean I have a little to relearn
<veebers> cgoldberg: you been up to much lately?
<cgoldberg> veebers, lots of performance related stuff at my gig... optimizing big web systems (django)
<cgoldberg> "make the web faster" kinda thing
<veebers> cgoldberg: nice, you enjoying it I take it?
<cgoldberg> yea.. it's nice.  the place I'm at is a non-profit with a pretty noble missions of delivering free education to the masses... we open source everything and have tons of contributors... overall pretty cool
<veebers> cgoldberg: sounds awesome :-)
<cgoldberg> and our entire server stack runs on Ubuntu
#ubuntu-autopilot 2015-03-18
<paulliu1> elopio: hi..
<paulliu> elopio: do you know how to let the stdout/stderr in platform-api to show when invoking autopilot3?
<paulliu> elopio: I'm debugging the shell rotation platform-api right now.
<elopio> paulliu: anything printed to stdout/stderr will be collected into the subunit result file.
<paulliu> elopio: what is a subunit result file? where can I find it?
<elopio> paulliu: in jenkins, that's the default output format and is collected in the artifacts.
<elopio> when running locally, you should use something like -f subunit -o /tmp/results
<elopio> paulliu: then you can use trv to see the results: http://paste.ubuntu.com/10621410/
<elopio> paulliu: we are trying to answer the questions with a vanguard. So next time you have a question, please go to #ubuntu-quality and ping the team as mentioned on the topic.
<elopio> paulliu: that way you won't have to wait for me to wake up, we have vanguard in european time zone.
<paulliu> elopio: cool thanks a lot.
<paulliu> elopio: got it.
<elopio> hey MacSlow, how are you getting your shell rotation branch in the phone?
<elopio> are you compiling it in the phone, or are you cross-compiling on desktop?
<MacSlow> elopio, I'm compiling it on the device
<paulliu> elopio: I just use run_on_device.sh to compile it on phone.
<elopio> I'll first try run_on_device.sh
<paulliu> elopio: the sensor-fifo seems didn't receive the fake commands.
<elopio> paulliu: for problems with that we need ricmm.
<paulliu> elopio: yeah. I'll talk to him. I'll get some log and find him.
<elopio> MacSlow: I'm trying to reproduce your problems, but keep getting distracted by urgent things of our sprint. If you think it would be useful to get some dedicated time pairing with us to get the automation problems solved, we need to schedule it in the next sprint.
<elopio> we have the meeting with the stakeholders in one hour, so you should talk to Kevin about bringing this topic to the meeting.
<MacSlow> elopio, since I'm stuck/blocked with this I would very much welcome some hangout/mumble time with you and/or rhuddie (whoever has time) on this.
<elopio> our next sprint starts tomorrow. And it lasts three weeks. I recommend you to talk to Kevin now, otherwise for the next three weeks we will have other priorities to work on and we'll be able to help you just in the "free time".
<MacSlow> elopio, just raising it with him
#ubuntu-autopilot 2015-03-24
<dobey> should autopilot bugs be filed against the ubuntu package or the upstream project? seems both are enabled on lp
 * balloons spins the wheel for dobey 
<balloons> dobey, personally I only file and look at the bugs on the upstream project
<dobey> "don't stop on github. don't stop on github"
<dobey> https://bugs.launchpad.net/autopilot/+bug/1435978
<ubot5> Ubuntu bug 1435978 in Autopilot "subunit file often missing attachments" [Critical,Triaged]
<balloons> ahh, you are filing that bug, nice
<dobey> well, i'm sure i'll be filing many bugs
<balloons> you can become veebers new best friend
<balloons> honestly though you could consider hacking on autopilot to fix them as well; it's not bad at all as a codebase
<dobey> for all i know, this bug isn't actually an issue in autopilot itself, and is just a result of the fact that testtools is so incredibly outdated in debian/ubuntu
<balloons> dobey, ohh.. that's a bigger can of worms
<balloons> but you already know about that, so nice work
<dobey> oh even more awesome
<dobey> linecache2 reqwuires unittest2 to be able to run the tests
<balloons> dobey, circluar dependencies?
<dobey> balloons: well, for the tests to work i guess, but not to be able to build the package itself
<dobey> whoo, got a linecache2 package built. going to see if i can get new unittest2/subunit built as well, and then hopefully will know for sure if this is an issue with subunit or autopilot
<dobey> or at least, will know if it's an issue fixed by new subunit or not
 * balloons wonders if dobey will feel happy or sad with his new knowledge
<balloons> I suppose if it's a testtools thing you can fix it right now yourself by installing the new package
<dobey> err new testtools, not subunit
<dobey> or maybe both. whatever
<dobey> yeah if it's a testtools thing, then i can at least just do a --setup-command with adt-run to add a PPA and install the new packages, until we can get them into ubuntu
<dobey> yeah, subunit is a bit behind too it seems
<dobey> whoot, and got new testtools built in a ppa on vivid
<dobey> now if it would just publish the binaries so that i can hit return in my other terminal to run some tests and see if it helps
<dobey> ooooooor not
<veebers> dobey: nice, there has been talk about getting the latest testtools synced
<dobey> apparently it requires some things that were backports of py3 things to py2, on py3 as well :-/
<dobey> veebers: yeah, i'm on that e-mail thread too :)
<veebers> dobey: ah cool :-)
<dobey> well, fail so far. will have to rebuild all this stuff tomorrow i guess
<dobey> long past my eod already. later :)
#ubuntu-autopilot 2015-03-25
<nik90> balloons: ping
<balloons> nik90, pong
<nik90> balloons: hey, could you run the clock-app trunk ap tests on your vivid desktop..I am getting failure as shown in http://paste.ubuntu.com/10678560/
<nik90> balloons: the failure seems to be at the UITK AP helpers
<balloons> nik90, sure.
<nik90> thnx :)
<balloons> nik90, I get a similar error
 * balloons updates and sees autopilot update
<nik90> balloons: hmm the obstacles to me fixing clock ap issue and releasing it to the store :P
 * nik90 updates
<balloons> nik90, same issue
<balloons> but, worth a try for updating.
<balloons> nik90, going to see if anything is a known issue
<nik90> balloons: after the update it got a little better (it was able to press the header button) but overall the test still failed..I am looking at it as well
<nik90> scratch what I said.. a couple of tries and it fails in the same way as before
<balloons> ahh.. so nik90 do we think the test is at fault here or no?
 * balloons has a look at the test
<balloons> interesting I see it failed on the header now
<nik90> balloons: well considering that the AP tests and the corresponding application code haven't been touched...I would doubt it being the test at fault here
<nik90> balloons: it seems to be changing..I see the header failure frequently
<balloons> right, that points to something else also
<nik90> and when the header fails, it points to the uitk helpers
<balloons> exactly. But sometimes it fails later. Anyways, let's see what some others think
<nik90> balloons: i have a hunch...clock-app crashes sometimes on vivid...this bug is being fixed and should land as an update to vivid asap. Could it be that?
<nik90> balloons: yup that has to be the issue! Testing the app manually also causes the crash at the exact point.
<nik90> balloons: I seem to be on a autopilot blaming spree recently..sry about that :/
<balloons> nik90, whoops.. that is usually the first thing I try when checking tests
<balloons> I didn't do that this time
<nik90> balloons: well I should have done that as well before bugging you about it :P
<balloons> no worries.. You triggered a memory in my brain anyway which will be helpful forme
<balloons> so, glad you mentioned it :-)
<dobey> OMG
#ubuntu-autopilot 2015-03-30
<tsdgeos> any idea how do i get rid of http://paste.ubuntu.com/10706760/ ?
#ubuntu-autopilot 2016-03-31
<bgr_> hello, can someone point me to the documentation for "autopilot3 run --config" command
<bgr_> I'm not sure if that's what I'm looking for, I'd like to see if I can tweak the mouse cursor speed somehow
<bgr_> ok, I've managed to speed it up by overriding the Mouse class
<bgr_> now I have a different question - how do I instruct autopilot to write the FailedTestScreenshot somewhere?
#ubuntu-autopilot 2017-03-16
<vigo> ahayzen, ping
<ahayzen> vigo, hey, what's up?
<vigo> ahayzen, :) heyy
<vigo> could you please take a look at this?
<vigo> https://trello.com/c/Bcq1nfg1/4041-2236-2236-ubuntu-printing-app-ubuntu-ui-extras-content-hub-qtubuntu-print-kenvandine-ahayzen
<vigo> I wrote down a couple of things that were not working for me
<ahayzen> vigo, yup, so the example-printing was only built for xenial, as we thought you'd be testing on that. I guess it can be build for zesty as well somehow.
<vigo> ahayzen, as we're now focusing in zesty would be great having it :)
<ahayzen> vigo, hmm that content-hub error shouldn't affect things, as it is address-book. I've also seen it before will need to remember what i did to get rid of it
<ahayzen> vigo, heh yeah, seems there is a sudden new focus on zesty when we were told previously only xenial would be supported :')
<ahayzen> vigo, i will need to check with ken how todo a build for zesty as the example-printing is a test package just for you guys :-) So will be later today when US comes online. And IIRC the content-hub error you should be able to safely ignore, but i'll double check
<vigo> ahayzen, perfect, well I can take it a look in xenial for the time being :)
<ahayzen> vigo, thanks :-)
<vigo> ahayzen, yw! and please let me know when everything is ready to party on zesty :)
<ahayzen> vigo, will do :-)
#ubuntu-autopilot 2018-03-12
<rast7> hi
<rast7> I have a doubt regarding unit testing using qml
<rast7> can someone help?

{'channel': 'ubuntu-autopilot', 'month': 3}