-
Notifications
You must be signed in to change notification settings - Fork 40
Move run operations from testcase
to run/serial
#428
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
Conversation
34c72ea
to
e16a70a
Compare
@altheaden, this is wonderful! The ocean tests all pass and are bit-for-bit with the previous version. I'll take a more careful look at the documentation soon, but probably not today. It will be easier to review once #413 goes in. |
8d78f38
to
fef3ade
Compare
@altheaden, you can rebase this as soon as you're ready. |
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.
A few suggestions on the documentation. It will be easier to do a full review of the docs after a rebase.
To inform people to use step.runtime_setup()
Also update outdated logging procedures
fef3ade
to
6a07053
Compare
@altheaden, I just rebased this branch. I tried to coordinate on Slack but I think you're busy with school having started last week for you. I just wanted to let you know that I'm going to move forward with this PR. |
56bc439
to
9cf9145
Compare
Including usage of runtime_setup() and constrain_resources()
5ff597b
to
b3ebaf0
Compare
Remove the deprecation warning from TestCase.run() because we actually do want ot run the (do-nothing) default implementaiton.
b3ebaf0
to
880ccc8
Compare
TestingI ran the ocean I also verified that the expected warnings appeared indicating deprecated overriding of
|
@matthewhoffman and @trhille, I'm not going to ask you to review this. I believe I've done enough testing to be sure that it does no harm to It doesn't appear that any test cases in |
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.
@altheaden, wonderful job!
I did a few final steps:
- rebased
- added the deprecation warning the way we discussed a couple of weeks ago
- fixed a few things in the documentation
Other than the deprecation warning itself (my fault!), everything worked perfectly on my first try!
I moved all run operations from
testcase.run()
and various other internal methods torun/serial
. This will allow future task parallel modifications to be limited to the run module. Therun()
method intestcase
will be deprecated in favor of usingstep.runtime_setup()
for custom setup operations at runtime.I have tested this change by running the
nightly
suite against the baseline without any issues. I'll be making some changes to the documentation as well to account for the changes to the framework.