-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Moose Server unit tests enforce unrelated things #27919
Comments
@brandonlangley can you generalize the test to allow for new params like we've done with some of the other tests? |
I ll address the MooseMesh parameter one for now. Thanks! |
I thought we had an issue for this but I'm too lazy to search rn |
ah yes I opened #26033 then we closed it after two fixes. I didnt realize there were more issues at the time |
@loganharbour - I just updated the MooseServerTest in #27924 so it will no longer fail when new input syntax is added. @GiudGiud - Depending on if my #27924 or your #27914 is merged first, one of us will resolve a conflict in that test file. |
This is still a problem. |
But this one is a little different, right? It was not caused by adding any new parameters or blocks. It was due to the existing
to now be:
While still technically unrelated, this will be a much more rare case than adding new input pieces. I'm not sure how to test the server (that assists MOOSE input) without testing a few input pieces. But it should rarely happen now and only need a small update when a tested piece gets changed. |
yes you're right. and in fact as you keep improving the test it will always be something a little different.
maybe it could be using pieces that are not supposed to change? like test objects. Or new objects created within the unit tests.
I did hit this like 1 week after than the second fix so I would not say it's rare yet. |
Bug Description
See this failure obtained after adding two valid parameters
Steps to Reproduce
Modify any class (moosemesh) or input feature that is caught in these unit tests and hardcoded to never change
Impact
This is slowing down other developments.
[Optional] Diagnostics
No response
The text was updated successfully, but these errors were encountered: