Ya It's been a little bit slow lately because of a high error rate in interactions with the git-hub API. Unfortunately we are pretty slammed for the release and haven't had a ton of time to do further debugging.
- Patrick On Tue, Mar 25, 2014 at 7:13 PM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > I just found that the Jenkins is not working from this afternoon > > for one PR, the first time build failed after 90 minutes, the second time it > has run for more than 2 hours, no result is returned > > Best, > > -- > Nan Zhu > > > On Tuesday, March 25, 2014 at 10:06 PM, Patrick Wendell wrote: > > That's not correct - like Michael said the Jenkins build remains the > reference build for now. > > On Tue, Mar 25, 2014 at 7:03 PM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > > I assume the Jenkins is not working now? > > Best, > > -- > Nan Zhu > > > On Tuesday, March 25, 2014 at 6:42 PM, Michael Armbrust wrote: > > Just a quick note to everyone that Patrick and I are playing around with > Travis CI on the Spark github repository. For now, travis does not run all > of the test cases, so will only be turned on experimentally. Long term it > looks like Travis might give better integration with github, so we are > going to see if it is feasible to get all of our tests running on it. > > *Jenkins remains the reference CI and should be consulted before merging > pull requests, independent of what Travis says.* > > If you have any questions or want to help out with the investigation, let > me know! > > Michael > >
