Replies: 2 comments 1 reply
-
|
Hello Nothing comes to mind rn. @permcody were there specific changes for unit tests to do? Guillaume |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The easy fix is to make sure the set of modules for your Unit Makefile
exactly matches your main application Makefile.
…On Tue, Sep 5, 2023 at 10:58 PM Guillaume Giudicelli < ***@***.***> wrote:
Hello
Nothing comes to mind rn. @permcody <https://github.com/permcody> were
there specific changes for unit tests to do?
Guillaume
—
Reply to this email directly, view it on GitHub
<#25406 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXFOIBSDVREPGNMMD26Z73XY77IHANCNFSM6AAAAAA4MM2TMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
smpark7
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working on a PR to remove various deprecated code in Moltres. After replacing
ModulesApp::registerAllwithModulesApp::registerAllObjects<MoltresApp>and other associated changes, the CI test for the PR fails at the "Build unit test" stage. Here's the link to the Civet test results: https://civet.inl.gov/job/1749366/It seems to be related to the Reactor module. Do I need to make additional changes to accommodate compiling
reactorwith Moltres?Beta Was this translation helpful? Give feedback.
All reactions