GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/3060
[SQL] Fixes race condition in CliSuite
`CliSuite` has been flaky for a while, this PR tries to improve this
situation by fixing a race condition in `CliSuite`. The `captureOutput`
function is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61400395
[Test build #22760 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22760/consoleFull)
for PR 3060 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61401913
[Test build #22760 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22760/consoleFull)
for PR 3060 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61401916
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61408595
retest this please
(The fixed issue is a race condition, would like to run multiple Jenkins
builds to verify.)
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61410827
[Test build #505 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/505/consoleFull)
for PR 3060 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61412774
[Test build #505 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/505/consoleFull)
for PR 3060 at commit
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61413463
aha, it explains the timeout issue. is there the same problem in
```HiveThriftServer2Suite```?
---
If your project is set up for it, you can reply to this email and have
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61413555
retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61413823
[Test build #22762 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22762/consoleFull)
for PR 3060 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61415950
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61415948
[Test build #22762 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22762/consoleFull)
for PR 3060 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/3060#issuecomment-61428712
Thanks for figuring this out! Merged to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3060
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
14 matches
Mail list logo
