Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Job Summary - Part 2 #1455

Merged
merged 31 commits into from
Jul 26, 2016
Merged

Job Summary - Part 2 #1455

merged 31 commits into from
Jul 26, 2016

Conversation

diptanu
Copy link
Contributor

@diptanu diptanu commented Jul 21, 2016

No description provided.

@diptanu diptanu force-pushed the f-job-summary branch 6 times, most recently from 405a11a to ff63033 Compare July 21, 2016 23:12
// Updating the allocs with the job id and task group name
for _, alloc := range req.Alloc {
if existing, _ := n.state.AllocByID(alloc.ID); existing != nil {
alloc.JobID = existing.JobID
Copy link
Contributor

Choose a reason for hiding this comment

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

If you are relying on this behavior I would add a unit test to ensure that this doesn't change

@dadgar
Copy link
Contributor

dadgar commented Jul 22, 2016

We need to handle the 0.4.0 -> 0.4.1 upgrade as the Job Summaries will not exist

summaries[0] = "Task Group|Queued|Starting|Running|Failed|Complete|Lost"
idx := 1
for tg, tgs := range summary.Summary {
summaries[idx] = fmt.Sprintf("%s|%d|%d|%d|%d|%d|%d",
Copy link
Contributor

Choose a reason for hiding this comment

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

Output this as well for the nomad status case

@diptanu diptanu force-pushed the f-job-summary branch 2 times, most recently from 0042f20 to 6e8bf9c Compare July 22, 2016 05:51
@diptanu diptanu merged commit 5081b94 into master Jul 26, 2016
@diptanu diptanu deleted the f-job-summary branch July 26, 2016 23:08
@dadgar dadgar mentioned this pull request Jul 27, 2016
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants