-
Notifications
You must be signed in to change notification settings - Fork 3
General JobType Coverage #338
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: master
Are you sure you want to change the base?
Conversation
This is a potentially breaking change. Before this we would simply log a warning if the configuration defined jobtype_default_environment and it was not a dictionary. From the perspective of job type implementor this would have been a silent failure and resulted in potentially unexpected behavior within a running job.
|
@guidow, PTAL. There's still some places I can add coverage, and plan to, but I figured this was probably complete enough that it's ready for review. |
|
There is a bit of a lull in my current project, so I'm taking some time to look at these PRs. Sorry again for keeping you waiting this long. This one fails a test on my machine: Apparently, a naming function for the CVS-log path uses a leading zero for the month in one place and no leading zero in another. This would also explain why the test passed with no apparent problems back in November... |
|
Other than that, this looks okay. |
Fix date format in test_uses_provided_create_time
…o jobtype_coverage
This adds additional tests for the JobType class and increases coverage without modifying the JobType class itself.