-
Notifications
You must be signed in to change notification settings - Fork 126
APP-10065: Record job completion times; include in GetMachineStatus #5493
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
base: main
Are you sure you want to change the base?
Conversation
fb80ee0 to
92b2c66
Compare
92b2c66 to
158f3bd
Compare
158f3bd to
6fe1130
Compare
6fe1130 to
63cefa1
Compare
63cefa1 to
d35568a
Compare
d35568a to
367ce5b
Compare
367ce5b to
80ff6ad
Compare
80ff6ad to
ba78f56
Compare
ba78f56 to
3d53de9
Compare
1275925 to
e076c4f
Compare
e076c4f to
ca0501d
Compare
a575750 to
7a6c5fd
Compare
7a6c5fd to
4b4d65d
Compare
…remove JobManager() from robot interface
4b4d65d to
503e408
Compare
cheukt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
generally LGTM, just a q around whether testing is complete
robot/impl/jobmanager_test.go
Outdated
| test.That(tb, len(failJob.RecentSuccessfulRuns), test.ShouldEqual, 0) | ||
| test.That(tb, len(failJob.RecentFailedRuns), test.ShouldBeGreaterThan, 0) | ||
| }) | ||
| // TODO: test flaky job with both successes and panics |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you adding another test here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Originally wasn't going to, as I don't think it adds much additional value (TODO msg just for completeness), but I don't mind quickly adding one.
690d285 to
93f3154
Compare
Basic implementation using an
ssync.MapofJobName -> 2x "container/ring".Lock contention is a potential issue, as
GetMachineStatusis called every second by each App tab open. It will be most noticeable on busy robots (with many App tabs open) that run frequent jobs (short-lived continuous and/or high count).Do we think it's worth optimizing further for this case?