-
Notifications
You must be signed in to change notification settings - Fork 57
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
implementing NekTestCase.run_neknek() #61
Comments
He wants to run a neknek short test so we need the same change in the Nek5000 repo.
…-----Original message-----
From:Ron Rahaman ***@***.***>
Sent: Wednesday 26th April 2017 12:57
To: Nek5000/NekExamples ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [Nek5000/NekExamples] implementing NekTestCase.run_neknek() (#61)
In #48 <#48>, I introduced nekBinRun.run_neknek(). We should also implement NekTestCase.run_neknek() as a wrapper.
cc: @kmittal2 <https://github.com/kmittal2>�
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#61>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ARumf5uPpybLbJ4FVt1vDWQX2FHz_FMCks5rz4XFgaJpZM4NJN2H>.
|
Understood. I opened Nek5000/Nek5000#257 as a duplicate. |
On a related note, it's becoming difficult to keep NekExamples/lib synched up in both Nek5000 and NekExamples. My suggestion: If NekExamples/lib is a separate repo, and is included as a submodule, it can stay synched between Nek5000 and NekExamples. I think some of us were opposed to submodules in the past, but I think they're incredibly useful. Any other suggestions? |
In #48, I introduced nekBinRun.run_neknek(). We should also implement NekTestCase.run_neknek() as a wrapper.
cc: @kmittal2
The text was updated successfully, but these errors were encountered: