Reporting Travis CI Failures

2019-01-14 Thread Hatem Helal
Hi everyone, I’ve had some trouble getting a clean CI build for a recent pull request and wanted to understand how this project manages CI failures. I don’t have much experience with Travis CI to draw on but my own approach so far has been to try and correlate failures on my own PR against oth

Re: Reporting Travis CI Failures

2019-01-14 Thread Wes McKinney
hi Hatem, There are various causes of flakiness in builds (for example, conda package manager timeouts) -- we have done our best so far to manage the flakiness and will continue to need to manage it. In such cases, you can git commit --amend && git push -f to restart builds without having to make

Re: Reporting Travis CI Failures

2019-01-14 Thread Hatem Helal
Hi Wes, Thanks for that - makes sense to me. How about this Xcode 6.4 failure? https://travis-ci.org/apache/arrow/jobs/479378190#L2427 I was hesitant to report this as the warning at the top of the page states that Xcode 6.4 is due to be deprecated this month. Thanks, Hatem On 1/14/19,

Re: Reporting Travis CI Failures

2019-01-14 Thread Wes McKinney
That can certainly be reported, particularly if you see it more than once On Mon, Jan 14, 2019 at 11:18 AM Hatem Helal wrote: > > Hi Wes, > > Thanks for that - makes sense to me. > > How about this Xcode 6.4 failure? > > https://travis-ci.org/apache/arrow/jobs/479378190#L2427 > > I was hesitant t