Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16098
Build started: [CORE] `org.apache.spark.JavaAPISuite`
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16098
**[Test build #69475 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69475/consoleFull)**
for PR 16098 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16098
**[Test build #69474 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69474/consoleFull)**
for PR 16098 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16098
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69467/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16098
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16098
**[Test build #69467 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69467/consoleFull)**
for PR 16098 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16098
(cc @mridulm as well who I guess is interested in this issue.)
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16098
Yes, it seems so because the output seems written in temp dir first and
then it is being renamed as the task is committed. Yes, let me try to neat up
as possible as I can.
---
If your project
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16098
I see, so the writer should be closed before committing?
Can the writer be closed before aborting too?
In that case, maybe it's cleaner to use nested try-finally? an inner
try-finally
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16098
**[Test build #69467 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69467/consoleFull)**
for PR 16098 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16098
Build started: [CORE] `org.apache.spark.JavaAPISuite`
11 matches
Mail list logo
