Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15355
I have re-enables the kafka test. This PR now only contains a change to
build infrastructure.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15355
**[Test build #66487 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66487/consoleFull)**
for PR 15355 at commit
[`a2ba414`](https://github.com/apache/spark/commit/a
Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/15355
@zsxwing good eye, thanks. It's not that auto.offset.reset.earliest
doesn't work, it's that there's a potential race condition that poll gets
called twice slowly enough for consumer position to b
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15355
@koeninger you can download the unit test logs from
https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-sbt-hadoop-2.6/1756/artifact/
I saw the offsets of the first batch (pat1 0 16
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15355
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66463/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15355
Merged build finished. Test PASSed.
---
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15355
**[Test build #66463 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66463/consoleFull)**
for PR 15355 at commit
[`5ba78b6`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15355
**[Test build #66463 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66463/consoleFull)**
for PR 15355 at commit
[`5ba78b6`](https://github.com/apache/spark/commit/5
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15355
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 project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15355
**[Test build #66461 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66461/consoleFull)**
for PR 15355 at commit
[`0bac9ff`](https://github.com/apache/spark/commit/0
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15355
**[Test build #66461 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66461/consoleFull)**
for PR 15355 at commit
[`0bac9ff`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15355
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66461/
Test FAILed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15355
Good point, I don't see separate config for the 0.10 module in
`dev/sparktestsupport/modules.py` though there is for 0.8 module. That could be
a better way forward.
---
If your project is set up fo
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15355
Actually we do have the infra to not run these tests if it is just an
unrelated module change. Was those not setup for Kafka?
---
If your project is set up for it, you can reply to this email and hav
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15355
Merged build finished. Test PASSed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15355
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66361/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15355
**[Test build #66361 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66361/consoleFull)**
for PR 15355 at commit
[`b7074d4`](https://github.com/apache/spark/commit/
Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/15355
I have generally been unable to reproduce these kinds of test failures on
my local environment, and don't have access to the build server, so trying fix
without repro is pretty much shooting rando
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15355
**[Test build #66361 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66361/consoleFull)**
for PR 15355 at commit
[`b7074d4`](https://github.com/apache/spark/commit/b
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15355
cc @koeninger any idea why this flaky?
---
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
e
20 matches
Mail list logo
