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
Add Report method to the Runner #5
Conversation
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.
Any chance we could have tests for the nested scenarios?
Would be nice to see output you expect to see from this :)
Adding some tests... |
576a77c
to
a96e025
Compare
a96e025
to
99f4bc1
Compare
!!build!! |
1 similar comment
!!build!! |
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.
This looks good to me, with the proviso that the dependency package is eventually going to move into here. (Or even just the report parts.) Otherwise it's a bit upside-down to have the library implement an interface for a specific program that uses it.
"state": info.status(), | ||
} | ||
if !info.started.IsZero() { | ||
workerReport["started"] = info.started.Format("2006-01-02 15:04:05") |
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.
Ugh, the weird date formatting thing always throws me.
|
The purpose of this work is to add a Report method to the Runner so we can see the nested reports in Juju for engines that nest runners.
As part of this work, I added the standard makefile and dependencies file. This highlighted licence mistakes, and to avoid bringing in juju/utils, just use juju/clock.