[15:55] <elopio> good morning!
[15:55] <balloons> morning elopio !
[15:56] <elopio> balloons: hello.
[16:34] <alesage> elopio you win at debugging u-s-s :) , what should we do next?
[16:35] <elopio> alesage: there are two remaining issues that I'm currently trying to reproduce.
[16:35] <elopio> then hope that jenkins agrees with my device that everything is actually less flaky now.
[16:35] <elopio> and that's it.
[16:35] <alesage> elopio, were you able to actually see the sound error outside of Jenkins?
[16:36] <elopio> alesage: yes.
[16:36] <alesage> elopio tell me more
[16:37] <elopio> alesage: when I ran the whole suite, I got tons of errors. I thought it was my device or config.
[16:37] <elopio> but after retrying the whole day, I realized it was not my fault.
[16:37] <elopio> so I started running one test, then its suite, then another test, then its suite.
[16:37] <alesage> elopio, I'm surprised by your result b/c the Jenkins logs always showed a sound test as the last
[16:38] <elopio> I found some errors there. But when I got to the test_phone* suite, I found that I could run the test individuallly, but not the whole suite.
[16:38] <alesage> elopio, aha b/c that one has *one* sound test
[16:38] <elopio> so I read the code, and found that they were starting the session bus, which is wrong.
[16:39] <alesage> is it possible to run autopilot with a list of tests to run, I wonder?
[16:39] <elopio> alesage: what happens on the jenkins runs I tried yesterday is that the run is killed. That's different from what I see on my phone, but could be caused by the same. I hope.
[16:39] <elopio> I'm going to make an MP to see how it goes.
[16:39] <alesage> elopio, is it always an error to start a separate session bus?
[16:40] <alesage> elopio, I tried MPs on the commits before and after ted added that, for the record, and found failures
[16:40] <alesage> possibly I was flummoxed by the new about errors
[16:41] <elopio> alesage: yes, this way it's always a problem. pitti and veebers discusssed like a month ago about adjusting the app so it works with a private bus. I think that would work.
[16:41] <alesage> elopio, anyway it would be very valuable for me to do a pairing session on your method :) , as we need a few more of you to support autopilot on our team
[16:41] <elopio> alesage: we have the session error, a couple more errors, and some flaky tests.
[16:41] <alesage> elopio, we should make a bug for that private session idea
[16:41] <elopio> I'm not sure how far back we would have to go to get a green run.
[16:42] <alesage> elopio, maybe "start over" :)
[16:42] <elopio> alesage: the problem with this is that if we start a hangout for a pairing session, most of the time is spend waiting for tests to run.
[16:43] <elopio> alesage: maybe you can try to reproduce the webbrowser problem that jibel is having. And we pair-debug it over IRC.
[16:43] <alesage> elopio, true waiting for Jenkins especially
[16:46] <alesage> elopio, we should maybe triage jibel's doc; if it goes over this week maybe the work should be scheduled?  or do you think just this week
[16:47] <elopio> alesage: not sure what are you talking about.
[16:48] <elopio> ah, that's an email. Let me read it.
[16:48] <alesage> elopio, from his new e-mail
[16:50] <elopio> alesage: yes, we should file bugs for most of the things he wants. We only have tomorrow to finish the tasks we started.
[16:53] <alesage> elopio, I'll go through and add bugs where they're missing and we can decide importance, etc.
[16:54] <elopio> alesage: thanks.
[17:14] <elopio> balloons: can you attend today's planning meeting?
[17:17] <balloons> elopio, yes i plan to
[17:17] <elopio> balloons: great.