14:00 <popey> #startmeeting Calendar app meeting
14:00 <meetingology> Meeting started Thu Feb 19 14:00:52 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
14:00 <meetingology> 
14:00 <meetingology> Available commands: action commands idea info link nick
14:00 <popey> hi Kunal
14:01 <Kunal> hi
14:01 <mihir> hey popey
14:01 <popey> hey mihir !
14:02 <popey> So, a couple of things.
14:02 <popey> We asked QA to test the calendar app currently in the store a few days ago.
14:02 <popey> http://pad.ubuntu.com/CalendarAppManualTesting  this was the manual testing guide I gave them
14:02 <popey> you probably saw a flurry of bugs and bug traffic as a result :)
14:03 <popey> The ultimate goal is (as always) to get it back in the default image.
14:03 <popey> But some of the bugs were seen as show stoppers.
14:03 <Kunal> ok
14:03 <mihir> ok
14:03 <popey> a couple of which are now fixed
14:03 <popey> but the lingering one is that the display doesn't show events when you first launch
14:03 <popey> which we're currently battling with https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/LiveEventModification/+merge/247711
14:03 <mihir> may be sync issue ?
14:04 <Kunal> yes, that MR was passing before
14:04 <Kunal> not sure what is going wrong there
14:04 <popey> and i have that merge installed on my nexus 7
14:04 <Kunal> now other MR's are passing
14:04 <popey> and it doesn't have the issue reported in the other bug
14:04 <popey> Now, I can't seem to run the autopilot tests here
14:05 <popey> (which I wanted to, to see what the issue is)
14:05 <popey> if you look at the last comment in the merge, vila says it loops for ~15 mins then gets killed
14:05 <Kunal> yes, i seen comment
14:05 <popey> i wanted to reproduce but can't run autopilot here.. (not tried for a while) - I get this:-
14:06 <Kunal> looks like its keep changing views
14:06 <popey> alan@deep-thought:~⟫ phablet-test-run calendar_app
14:06 <popey> /bin/bash: autopilot3: command not found
14:06 <Kunal> right, now its needs autopilot3
14:06 <Kunal> not autopilot
14:06 <Kunal> you will need to install it, not sure how it can be done phone
14:07 <popey> guess i need to make my device writable to install it, okay
14:08 <Kunal> BTW this MR is passing now
14:08 <Kunal> https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/TimePickerHeight/+merge/249922
14:08 <Kunal> please review
14:08 <popey> ah, awesome
14:08 <popey> will do after I kick autopilot3
14:08 <Kunal> ok :)
14:09 <Kunal> I will also try running AP, on my setup
14:11 <Kunal> also, which other blockers we are talking about,
14:11 <Kunal> is there some tag
14:12 <popey> yes.
14:12 <popey> https://bugs.launchpad.net/ubuntu-calendar-app/+bugs?field.tag=required-for-landing
14:12 <popey> (yay, autopilot running)
14:13 <popey> during the landing call this morning, we suggested that we'd send the app for testing again next week
14:13 <popey> which is why I'm keen to get stuff landed asap so we can test it first and identify these issues before they do, and bounce it back to us
14:13 <Kunal> related to sync
14:13 <Kunal> looks like only one issue is pending
14:15 <popey> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1362781 that one?
14:15 <Kunal> yes
14:18 <popey> ok
14:19 <Kunal> i also commented on one bug which you reported
14:19 <Kunal> related to removing disabled calendars
14:19 <Kunal> we need support from EDS
14:21 <popey> ok.
14:21 <popey> so I ran AP tests twice
14:21 <popey> http://paste.ubuntu.com/10308601/
14:21 <popey> no idea what's going on here
14:22 <mihir> popey: you might be missing addressbook package
14:22 <mihir> can you check debian/control ?
14:23 <mihir> and you have all the pacakges ?
14:23 <popey> address-book-app is installed
14:23 <popey> yeah, i have everything listed in control
14:23 <popey> paging balloons!
14:24 <mihir> ok
14:25 <popey> the timepicker one looks good to me
14:25 <Kunal> ok
14:25 <popey> the target is much larger
14:25 <Kunal> as  such, i dont see anything wrong in log
14:25 <Kunal> need to check more
14:26 * popey approves
14:26 <Kunal> great :)
14:26 <popey> one down!
14:27 <popey> I'll work with balloons to figure out what's wrong with the other one.
14:28 <balloons> ohh, you want me?
14:29 <popey> hello
14:29 <popey> balloons: https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/LiveEventModification/+merge/247711 is causing pain
14:29 * balloons couldn't figure out why his irc client kept pinging him..
14:29 <popey> and I'm trying to run the tests on my device and I get more pain
14:29 <popey> http://paste.ubuntu.com/10308601/
14:29 <Kunal> popey: can you install this package
14:29 <Kunal> python-autopilot-trace
14:30 <popey> ok
14:30 <Kunal> may be after that can get some more information
14:31 <Kunal> but to me it seem test passed
14:31 <balloons> ok, so jenkins passed, but now won't autoland. And you are having trouble running on the device
14:31 <Kunal> INFO testresult:44 - OK: calendar_app.tests.test_data.EventTestCase.test_make_unique_event_must_return_event_with_unique_id
14:31 <popey> wow, that pulls in a lot
14:31 <balloons> it's python2, presumably, python3-autopilot-trace
14:31 <balloons> ?
14:32 <balloons> indeed..
14:32 <popey> ah
14:35 * popey runs again
14:35 <Kunal> popey: I need to leave now,  I will try watch bugs and see what I can do
14:35 <popey> ok Kunal thanks!
14:35 <Kunal> do let me know, if you need something else
14:35 <popey> have a great weekend
14:35 <popey> will do
14:35 <Kunal> bye
14:36 <Kunal> you too
14:36 <balloons> so the jenkins log shows the tests timing out and being killed
14:36 <balloons> endlessly looping on moving and pressing the mouse
14:38 <popey> yes
14:39 <balloons> both cases are in test_show_next_weeks.. should be simple enough to have a look at what would cause that
14:41 * balloons sees the offending code
14:42 <balloons> so popey if this will land, land it. Otherwise it will depend on this being fixed. Either way I think a simple bug being opened describing the issue should suffice as it affects trunk.
14:43 <balloons> The issue is in the change week swiping; it might be doing this now because they changed the default xpad values (I remember them doing that)
14:44 <balloons> bah, nope it doesn't use xpad.. well, anyways, simple enough to fix and the logic shouldn't have an endless loop in it anyway
14:44 <popey> but I can't land it
14:44 <popey> it fails in autolanding
14:46 <balloons> right, if it will always do that, I guess we're stuck waiting. It might even be his changes that trigger it
14:47 <balloons> shall I open the bug?
14:47 <popey> that would be super
14:50 <popey> lets wrap this meeting for now.
14:50 <popey> #endmeeting