-
Notifications
You must be signed in to change notification settings - Fork 318
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
experiment bug fix #2435
experiment bug fix #2435
Conversation
Assigning this to @slevis-lmwg to integrate into b4b-dev after @ekluzek is able to approve the PR. |
I should add that I was able to create --transient cases with code mods on this branch. |
@TeaganKing I also see this is marked as a WIP. Was there more you were planning to add to this PR? |
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.
Marking as approved since it's small and I see no problems with the changes.
This is still marked as a draft, is this ready to come in? Or is there more going on here?
I wasn't sure about the removal of the default values from run_case. Can you elaborate more on why that's being done?
@wwieder I was planning to add fixes for other issues in the same PR, but I think maybe we should keep this as simple as possible since there are lots of moving pieces right now. I wasn't planning to add anything else specifically for the 'experiment' functionality. |
Merging b4b-neon instead of b4b-dev because I expect to push b4b-neon to b4b-dev soon
Testing after merging b4b-neon to this branch (thus, effectively, having merged the latest b4b-dev): @TeaganKing two requests:
I think I should send this back to you to fix, unless @wwieder would rather I did the rest of the debugging on this. |
Thanks for catching that, @slevis-lmwg . I added you to the repository. I'm not going to be able to fix the system test error tonight, but I think I see what's going on and should have time to fix it tomorrow. |
Thank you, @TeaganKing |
@TeaganKing is this something that's straight forward for you to address? Sorry, I wrote this without refreshing my browser looking upstream on the conversation. Thanks @TeaganKing |
Hi @slevis-lmwg, I think I fixed the issue. |
…on_experiment_fix
Testing this morning passed: |
For my own sanity, I'm also running derecho OK |
This PR involves some changes to the arguments in run_case in order to address #2433
Fixes #2433