Josh:
We're on the same page.
I used the term 're-submit your PR' which was different from opening new PR.
On Mon, Oct 12, 2015 at 2:47 PM, Personal wrote:
> Just ask Jenkins to retest; no need to open a new PR just to re-trigger
> the build.
>
>
> On October 12, 2015 at 2:45:13 PM, Ted Yu (yuz
Just ask Jenkins to retest; no need to open a new PR just to re-trigger the
build.
On October 12, 2015 at 2:45:13 PM, Ted Yu (yuzhih...@gmail.com) wrote:
Can you re-submit your PR to trigger a new build - assuming the tests are flaky
?
If any test fails again, consider contacting the owner of
Can you re-submit your PR to trigger a new build - assuming the tests are
flaky ?
If any test fails again, consider contacting the owner of the module for
expert opinion.
Cheers
On Mon, Oct 12, 2015 at 2:07 PM, Meihua Wu
wrote:
> Hi Ted,
>
> Thanks for the info. I have checked but I did not fi
Hi Ted,
Thanks for the info. I have checked but I did not find the failures though.
In my cases, I have seen
1) spilling in ExternalAppendOnlyMapSuite failed due to timeout.
[https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43531/console]
2) pySpark failure
[https://amplab.cs.
You can go to:
https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-Maven-with-YARN
and see if the test failure(s) you encountered appeared there.
FYI
On Mon, Oct 12, 2015 at 1:24 PM, Meihua Wu
wrote:
> Hi Spark Devs,
>
> I recently encountered several cases that the Jenkin failed tests tha
Hi Spark Devs,
I recently encountered several cases that the Jenkin failed tests that
are supposed to be unrelated to my patch. For example, I made a patch
to Spark ML Scala API but some Scala RDD tests failed due to timeout,
or the java_gateway in PySpark fails. Just wondering if these are
isolat