Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114601354
Merged build started.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114602102
[Test build #35568 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35568/consoleFull)
for PR 6917 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114601327
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114209774
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114209751
Merged build triggered.
---
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
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114211896
hi @andrewor14 - I agree with @rxin here. We should probably use the
framework's tagging mechanism, no?
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114233442
Merged build finished. Test FAILed.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-11425
[Test build #35466 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35466/console)
for PR 6917 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114212881
@harishreedharan we discussed offline and already agreed on special tags.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114213931
Cool, thank you!
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114210536
[Test build #35466 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35466/consoleFull)
for PR 6917 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114209598
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/6917#issuecomment-113722822
[Test build #35356 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35356/console)
for PR 6917 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113722910
Merged build finished. Test FAILed.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113714893
[Test build #35353 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35353/console)
for PR 6917 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113714942
Merged build finished. Test FAILed.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113716861
[Test build #35356 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35356/consoleFull)
for PR 6917 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113716858
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113716853
Merged build triggered.
---
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113716774
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 andrewor14 opened a pull request:
https://github.com/apache/spark/pull/6917
[SPARK-8496] [Tests] Do not run slow tests for every PR
The purpose of this patch is to speed up the development cycle by
separating slow tests from normal tests. The intention is to run slow
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113709883
[Test build #35353 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35353/consoleFull)
for PR 6917 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113711786
Can we just use scalatest's tags for this?
---
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113712088
what do you mean?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113709833
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113709826
Merged build triggered.
---
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-113712683
It is a feature of ScalaTest -- you can tag individual test cases. And then
at runtime you can specify to rule out specific tags, or only run specific
tags. See
27 matches
Mail list logo
