-
Notifications
You must be signed in to change notification settings - Fork 37
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
Unit tests for ShellLauncher & additional shell launch context #671
Unit tests for ShellLauncher & additional shell launch context #671
Conversation
REBASEME: moar mpi REBASEME: fmt mpi
tests/test_shell_launcher.py
Outdated
# TODO tests bad vars in Popen call at beginning | ||
# tests -> helper.exe : pass in None, empty str, path with a space at beginning, a non valid command | ||
# -> write a test for the invalid num of items - test_shell_launcher_fails_on_any_invalid_len_input | ||
# -> have border tests for 0,1,4,6 cmd vals -> work correctly without them -> raise ValueError | ||
# do all of the failures as well as the sucess criteria |
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.
Is this TODO still needed? I think I saw some of this being tested, but not all. Is this something we want to address in this PR or a follow on? If a follow on, is there a ticket somewhere for this work??
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.
- invalid num of items is not required given that it was written down during the era of unpacking a tuple and expecting the length to be #.
- I do not believe border tests for cmd vals is necessary given the new NamedTuple
- can probably add a check for popen cwd
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.
Looks great! Just a little bit of nit picking, but otherwise looks about ready to go on my end!!
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.
Some minor nits on the shell launcher tests, but nothing worth holding approval up over!
LGTM, thanks for all the hard work on this! Now that we are successfully generating logs to the right spot for all of our primitive jobs we are shaping up to be in really good shape for the V1 API!!
f9a86d9
into
CrayLabs:smartsim-refactor
No description provided.