Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17538
**[Test build #75541 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75541/testReport)**
for PR 17538 at commit
[`5fa2ced`](https://github.com/apache/spark/commit/5f
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17538
Looks like a typo, yes, but I wonder how this worked at all? is it not used?
---
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 pr
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17538
**[Test build #75541 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75541/testReport)**
for PR 17538 at commit
[`5fa2ced`](https://github.com/apache/spark/commit/5
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17538
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75541/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17538
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 wzhfy commented on the issue:
https://github.com/apache/spark/pull/17538
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 feature
enabled and wishes so, or
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/17538
@srowen There's a benchmark test `TPCDSQueryBenchmark` that user can run,
so I think it should be fixed.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17538
**[Test build #75546 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75546/testReport)**
for PR 17538 at commit
[`5fa2ced`](https://github.com/apache/spark/commit/5f
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17538
@wzhfy yeah it's a dumb question maybe, but is that not run automatically
and thus why it isn't caught by tests?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17538
**[Test build #75546 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75546/testReport)**
for PR 17538 at commit
[`5fa2ced`](https://github.com/apache/spark/commit/5
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17538
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75546/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17538
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17538
I think we are not running it in our test case batches. This is for
performance evaluation.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17538
Thanks! Merging to master/2.1/2.0
---
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
enable
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/17538
@srowen It's not run automatically. And even if it is run, no error would
be caught, the predicate will just become `null` because casting
`'2000-08-03]'` to Date is failed.
---
If your project is s
15 matches
Mail list logo