Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17011
Don't run things as root. Please close this PR.
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/17011
@srowen @vanzin I think the root cause is I test it in root user. So it
always be readable no matter what access permission. IMHO, it is OK to add once
extra access permission check, as the code
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/17011
@srowen @vanzin I will test in some other platforms.
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/17011
Yes, this is pretty weird. Especially since I've never seen this test fail
nor heard about anyone else having seen it fail. If you can point out in the
Hadoop code where that discrepancy can occur,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73218/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17011
**[Test build #73218 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73218/testReport)**
for PR 17011 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17011
I don't quite see why it can succeed in listing a file that's not readable,
later in mergeApplicationListing? won't that fail or generate an error already?
Therefore I'm wondering if this is really
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73206/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17011
**[Test build #73206 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73206/testReport)**
for PR 17011 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17011
**[Test build #73218 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73218/testReport)**
for PR 17011 at commit
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/17011
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17011
**[Test build #73206 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73206/testReport)**
for PR 17011 at commit
14 matches
Mail list logo
