Yeah, it feels like Jenkins has become a lot more flaky recently. Or maybe
it’s just our tests.

Here are some more examples:

   - https://github.com/apache/spark/pull/2310#issuecomment-54741169
   - https://github.com/apache/spark/pull/2313#issuecomment-54752766

Nick
​

On Sun, Sep 7, 2014 at 4:54 PM, Nan Zhu <zhunanmcg...@gmail.com> wrote:

> It seems that I’m not the only one
>
> https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/
>
> Best,
>
> --
> Nan Zhu
>
>
> On Sunday, September 7, 2014 at 4:52 PM, Nan Zhu wrote:
>
> > Hi, Sean,
> >
> > Thanks for the reply
> >
> > Here are the updated files:
> >
> > https://github.com/apache/spark/pull/2312/files
> >
> > just two md files...
> >
> > Best,
> >
> > --
> > Nan Zhu
> >
> >
> > On Sunday, September 7, 2014 at 4:30 PM, Sean Owen wrote:
> >
> > > It would help to point to your change. Are you sure it was only docs
> > > and are you sure you're rebased, submitting against the right branch?
> > > Jenkins is saying you are changing public APIs; it's not reporting
> > > test failures. But it could well be a test/Jenkins problem.
> > >
> > > On Sun, Sep 7, 2014 at 8:39 PM, Nan Zhu <zhunanmcg...@gmail.com
> (mailto:zhunanmcg...@gmail.com)> wrote:
> > > > Hi, all
> > > >
> > > > I just modified some document,
> > > >
> > > > but still failed to pass tests?
> > > >
> > > >
> https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19950/consoleFull
> > > >
> > > > Anyone can look at the problem?
> > > >
> > > > Best,
> > > >
> > > > --
> > > > Nan Zhu
> > > >
> > >
> > >
> > >
> > >
> >
> >
>
>

Reply via email to