Skip to content

Conversation

@lianhuiwang
Copy link
Contributor

We should have a "kill" link for each job, similar to what we have for each stage, so it's easier for users to kill jobs in the UI. @kayousterhout can you take a look at this? thanks.

@SparkQA
Copy link

SparkQA commented Feb 28, 2015

Test build #28107 has started for PR 4823 at commit af461cc.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Feb 28, 2015

Test build #28107 has finished for PR 4823 at commit af461cc.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28107/
Test PASSed.

@SparkQA
Copy link

SparkQA commented Feb 28, 2015

Test build #28112 has started for PR 4823 at commit 7f52874.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Feb 28, 2015

Test build #28112 has finished for PR 4823 at commit 7f52874.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28112/
Test PASSed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few tiny comments to consider, if you have to otherwise make changes to this PR: this might be easier to read with string interpolation

@SparkQA
Copy link

SparkQA commented Mar 1, 2015

Test build #28140 has started for PR 4823 at commit 584240a.

  • This patch merges cleanly.

@lianhuiwang
Copy link
Contributor Author

@srowen i have update for your comments. can you take a look again. thanks.

@SparkQA
Copy link

SparkQA commented Mar 1, 2015

Test build #28142 has started for PR 4823 at commit 25fc0fd.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Mar 1, 2015

Test build #28140 has finished for PR 4823 at commit 584240a.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28140/
Test FAILed.

@SparkQA
Copy link

SparkQA commented Mar 1, 2015

Test build #28142 has finished for PR 4823 at commit 25fc0fd.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28142/
Test PASSed.

@srowen
Copy link
Member

srowen commented Mar 1, 2015

OK by me; would be good to let @kayousterhout give it a thumbs up.

@andrewor14
Copy link
Contributor

@JoshRosen @kayousterhout what do you think

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please add : Unit return type here (and other places)

@SparkQA
Copy link

SparkQA commented Mar 24, 2015

Test build #29064 has started for PR 4823 at commit ba16839.

  • This patch does not merge cleanly.

@SparkQA
Copy link

SparkQA commented Mar 24, 2015

Test build #29064 has finished for PR 4823 at commit ba16839.

  • This patch passes all tests.
  • This patch does not merge cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29064/
Test PASSed.

@SparkQA
Copy link

SparkQA commented Mar 25, 2015

Test build #29135 has started for PR 4823 at commit a0eee0c.

  • This patch does not merge cleanly.

@SparkQA
Copy link

SparkQA commented Mar 25, 2015

Test build #29135 has finished for PR 4823 at commit a0eee0c.

  • This patch fails Spark unit tests.
  • This patch does not merge cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29135/
Test FAILed.

@srowen
Copy link
Member

srowen commented Jun 16, 2015

I think this would have to be rebased at least, and rewritten to match the new kill link behavior elsewhere. Can this be closed?

ajbozarth added a commit to ajbozarth/spark that referenced this pull request Oct 11, 2016
ghost pushed a commit to dbtsai/spark that referenced this pull request Oct 26, 2016
## What changes were proposed in this pull request?

Currently users can kill stages via the web ui but not jobs directly (jobs are killed if one of their stages is). I've added the ability to kill jobs via the web ui. This code change is based on apache#4823 by lianhuiwang and updated to work with the latest code matching how stages are currently killed. In general I've copied the kill stage code warning and note comments and all. I also updated applicable tests and documentation.

## How was this patch tested?

Manually tested and dev/run-tests

![screen shot 2016-10-11 at 4 49 43 pm](https://cloud.githubusercontent.com/assets/13952758/19292857/12f1b7c0-8fd4-11e6-8982-210249f7b697.png)

Author: Alex Bozarth <[email protected]>
Author: Lianhui Wang <[email protected]>

Closes apache#15441 from ajbozarth/spark4411.
robert3005 pushed a commit to palantir/spark that referenced this pull request Nov 1, 2016
## What changes were proposed in this pull request?

Currently users can kill stages via the web ui but not jobs directly (jobs are killed if one of their stages is). I've added the ability to kill jobs via the web ui. This code change is based on apache#4823 by lianhuiwang and updated to work with the latest code matching how stages are currently killed. In general I've copied the kill stage code warning and note comments and all. I also updated applicable tests and documentation.

## How was this patch tested?

Manually tested and dev/run-tests

![screen shot 2016-10-11 at 4 49 43 pm](https://cloud.githubusercontent.com/assets/13952758/19292857/12f1b7c0-8fd4-11e6-8982-210249f7b697.png)

Author: Alex Bozarth <[email protected]>
Author: Lianhui Wang <[email protected]>

Closes apache#15441 from ajbozarth/spark4411.
uzadude pushed a commit to uzadude/spark that referenced this pull request Jan 27, 2017
## What changes were proposed in this pull request?

Currently users can kill stages via the web ui but not jobs directly (jobs are killed if one of their stages is). I've added the ability to kill jobs via the web ui. This code change is based on apache#4823 by lianhuiwang and updated to work with the latest code matching how stages are currently killed. In general I've copied the kill stage code warning and note comments and all. I also updated applicable tests and documentation.

## How was this patch tested?

Manually tested and dev/run-tests

![screen shot 2016-10-11 at 4 49 43 pm](https://cloud.githubusercontent.com/assets/13952758/19292857/12f1b7c0-8fd4-11e6-8982-210249f7b697.png)

Author: Alex Bozarth <[email protected]>
Author: Lianhui Wang <[email protected]>

Closes apache#15441 from ajbozarth/spark4411.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants