Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14804
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14804
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72944/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14804
**[Test build #72944 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72944/testReport)**
for PR 14804 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14804
**[Test build #72944 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72944/testReport)**
for PR 14804 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14804
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14804
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64410/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14804
**[Test build #64410 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64410/consoleFull)**
for PR 14804 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14804
Meh, it's still ambiguous and there's a defined way to disambiguate, so
it's unfortunate, but I'm OK with a step towards consistency in any event.
---
If your project is set up for it, you can
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/14804
I think
[here](http://ux.stackexchange.com/questions/13815/files-size-units-kib-vs-kb-vs-kb)
has a precise definition. AFAIK in Spark the conversion is 1024 based either
KB, K, or kb, KiB is not
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14804
Ugh, yeah that's wrong in the sense that we are not showing MB, but MiB.
I'd favor fixing the labels here and in Utils.bytesToString?
Then again, I see that we will also parse input of
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/14804
Because in the log it shows Memory MB in 1024 based, while in the web UI it
is 1000 based, so this is slightly different.
You could check `Utils#bytesToString`. I think we unify this.
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14804
KB = 1000 bytes, KiB = 1024 bytes. According to the suffixes we're using,
1000 is correct at the moment. Is the display inconsistent with something else
in the UI or logs?
---
If your project is
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14804
**[Test build #64410 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64410/consoleFull)**
for PR 14804 at commit
13 matches
Mail list logo
