-
Notifications
You must be signed in to change notification settings - Fork 133
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
Loop over all Butcher tables to test order #488
Conversation
Is there any need to do outfile checking for this test? Isn't the return code of the test enough? |
That's a good question, since I also do not fully understand the use of |
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.
Once this passes the CI tests (it may need a new .out file, either in this repo or in the answers repo), this looks good to me.
@Steven-Roberts A couple of follow-on items to this PR:
|
Actually, no need to update |
Ok, looks like I'll need a separate PR to do that now that this is merged. |
I always forget about this nice sphinx feature |
Address a couple missing things noted in #488 after it was merged. --------- Co-authored-by: David Gardner <gardner48@llnl.gov>
Switches from a vector of table names (which was often not updated) to iterating over the enum of tables so methods get included in this test automatically.
Address a couple missing things noted in #488 after it was merged. --------- Co-authored-by: David Gardner <gardner48@llnl.gov>
Switches from a vector of table names (which was often not updated) to iterating over the enum of tables so methods get included in this test automatically.