Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149463366
**[Test build #43964 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43964/consoleFull)**
for PR 9059 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149463526
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9059
---
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 the feature is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149463523
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149465372
Merged to master
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149192174
**[Test build #1927 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1927/consoleFull)**
for PR 9059 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149220943
**[Test build #1928 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1928/consoleFull)**
for PR 9059 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149220700
It's different failures each time, and almost certainly spurious but trying
again.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149218788
**[Test build #1927 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1927/consoleFull)**
for PR 9059 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149248356
@jbonofre Those failures may be caused by flaky some tests.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149239618
Thanks Sean. I tried on my box and it works fine. I gonna check Jenkins
result.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149248961
Yeah, I already have some random failures/flaky tests. I plan to work on it
as well ;)
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149258901
**[Test build #1928 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1928/consoleFull)**
for PR 9059 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149296224
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149301756
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149297487
Merged build started.
---
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
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149297361
Right now, if endTime is greater than 0, it means that we are on the
history server, so we use it. Else, it means the application is running, to we
can use
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149297439
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149301758
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149374116
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149377315
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149377318
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149437141
@sarutak I'm retesting. I keep you posted. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149437223
It looks not related to the PR: ERROR: Timeout after 15 minutes
ERROR: Error fetching remote repo 'origin'
---
If your project is set up for it, you can reply to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149438729
**[Test build #43964 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43964/consoleFull)**
for PR 9059 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149437438
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149437462
Merged build started.
---
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
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149437012
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149025020
[Test build #1923 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1923/consoleFull)
for PR 9059 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149024960
@jbonofre I think you're welcome to fix SPARK-5179 but it need not be here.
I think @andrewor14 was saying he supported the change since the existing logic
made the
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149029916
OK, let me check SPARK-5179 so. I'm on SPARK-6541 as well (not related).
Thanks @srowen !
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-149032532
[Test build #1923 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1923/console)
for PR 9059 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148805581
Merged build started.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148807086
[Test build #43845 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43845/consoleFull)
for PR 9059 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148805547
Merged build triggered.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148835246
[Test build #43845 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43845/console)
for PR 9059 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148835351
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148835352
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148887378
@andrewor14 thanks for the update. Let me check about the bogus value. I
keep you posted.
---
If your project is set up for it, you can reply to this email and have
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148887467
@andrewor14 it sounds the same as in SPARK-5179, right ? Do you want that I
fix in this PR or I do another one dedicated to SPARK-5179 ? Thanks.
Regards
JB
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148804983
This change looks good. Right now the history server displays a bogus value
based on `System.currentTimeMillis`. Let's retest this please.
---
If your project is
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148249953
Yeah, I'll check it out soon.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148031058
[Test build #1896 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1896/console)
for PR 9059 at commit
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148036569
Regarding the test result, it looks like the failure comes from spark.sql:
[info] - SPARK-8406: Avoids name collision while writing files (3 seconds,
113
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148036672
Hi @sarutak, do you mind to review the last change ?
Thanks in advance,
Regards
JB
---
If your project is set up for it, you can reply to this email
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148032657
I'm checking why the utests fail (if it's really related).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148005865
[Test build #1896 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1896/consoleFull)
for PR 9059 at commit
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41831148
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -289,13 +290,15 @@ private[ui] class AllJobsPage(parent: JobsTab)
extends
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41837372
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -289,13 +290,15 @@ private[ui] class AllJobsPage(parent: JobsTab)
extends
Github user jbonofre commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41839587
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -289,13 +290,15 @@ private[ui] class AllJobsPage(parent: JobsTab)
extends
Github user jbonofre commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41837043
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -289,13 +290,15 @@ private[ui] class AllJobsPage(parent: JobsTab)
extends
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41768301
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -289,13 +290,14 @@ private[ui] class AllJobsPage(parent: JobsTab)
extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-147439152
[Test build #1875 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1875/consoleFull)
for PR 9059 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-147448778
I applied your patch and I noticed you didn't care the case we watch the
status of incomplete apps through the history server.
Sometimes, apps are marked as
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-147411507
Updated PR with a minor cleanup in the total uptime computation. @srowen I
double checked and I confirm that the history server view is updated (as the
application
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-147472175
[Test build #1875 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1875/console)
for PR 9059 at commit
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-147459912
Thanks for the feedback. I will enhance as you said. Thanks again !
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-147601229
@sarutak what do you think about the last PR update ? I test the endTime
value, and if it's negative (meaning incomplete apps), I fallback to current
time. Thanks !
Github user jbonofre commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41828864
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -289,13 +290,13 @@ private[ui] class AllJobsPage(parent: JobsTab)
extends
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41826841
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -289,13 +290,13 @@ private[ui] class AllJobsPage(parent: JobsTab)
extends
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41706707
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -295,6 +296,12 @@ private[ui] class AllJobsPage(parent: JobsTab) extends
Github user jbonofre commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41706941
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -295,6 +296,12 @@ private[ui] class AllJobsPage(parent: JobsTab) extends
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-147170429
@jbonofre you don't need to make a new PR. Push more commits to this branch.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-147171894
It's what I meant in my last comment ;)
---
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 jbonofre commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41706141
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -295,6 +296,12 @@ private[ui] class AllJobsPage(parent: JobsTab) extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-147046546
Can one of the admins verify this patch?
---
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
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41695300
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -295,6 +296,12 @@ private[ui] class AllJobsPage(parent: JobsTab) extends
GitHub user jbonofre opened a pull request:
https://github.com/apache/spark/pull/9059
SPARK-10876 - Display total uptime for completed applications
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbonofre/spark SPARK-10876
68 matches
Mail list logo
