Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17290
No, https://issues.apache.org/jira/browse/SPARK-16599 is still open
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache
Github user aphasingnirvana commented on the issue:
https://github.com/apache/spark/pull/17290
@srowen So could I open another issue altogether?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17290
I don't think this change was the ultimate fix, and it caused another
problem, so no I don't think this PR should be reopened.
---
--
Github user aphasingnirvana commented on the issue:
https://github.com/apache/spark/pull/17290
@srowen I believe the bug still persists. Shouldn't we reopen it?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/17290
I agree with @srowen I dont see how this change affects the test.
`blocksWithReleasedLocks` should be unchanged w.r.t this test.
---
If your project is set up for it, you can reply to this email an
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17290
Hm, that concerns me @gatorsmile . Without this change I might expect that
it would have also failed, just in the same way the JIRA describes.
I could add a warning for the case where there i
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17290
Without code changes,
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74836/ still
can pass after triggering a retest. I think it is not related to this PR.
---
If your proje
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17290
After removing the changes in this PR, the test case passed in my local
environment. I think we need to revert it back.
---
If your project is set up for it, you can reply to this email and have
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17290
As found in https://github.com/apache/spark/pull/17338, I am afraid this
one caused the following test failure.
- proactive block replication - 4 replicas - 3 block manager deletions ***
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17290
That's fine I can add a warning. I don't know if it is a bug situation but
it sure could be.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17290
Merged to master. I don't believe this necessarily resolves the JIRA.
---
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 d
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17290
I'd like to merge this as a step towards possibly resolving the problem or
uncovering its root.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17290
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/17290
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74526/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17290
**[Test build #74526 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74526/testReport)**
for PR 17290 at commit
[`5da4bcf`](https://github.com/apache/spark/commit/5
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17290
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74523/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17290
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/17290
**[Test build #74523 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74523/testReport)**
for PR 17290 at commit
[`27234e1`](https://github.com/apache/spark/commit/2
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17290
**[Test build #74523 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74523/testReport)**
for PR 17290 at commit
[`27234e1`](https://github.com/apache/spark/commit/27
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17290
CC @JoshRosen
---
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 t
20 matches
Mail list logo
