-
Notifications
You must be signed in to change notification settings - Fork 51
Build: Multithread IDL Tests #2780
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
base: alpha
Are you sure you want to change the base?
Build: Multithread IDL Tests #2780
Conversation
de6e94b to
5c808ef
Compare
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.
Have confirmed that this refactoring of the IDL test suite is suitable for multi-threading of the "read" tests. So approving this PR.
There is a trivial formatting / style issue at line ~380 which is an extraneous blank line. It is OK to leave it "as is".
We'll likely have to run this multi-threaded read test for a week or so before we can be confident that the connection stress tests (60 to 100 connections per test case) won't clash when run in parallel.
5c808ef to
885bdf6
Compare
First attempt at multithreading the IDL tests TODO: The write tests still need a way to access mdsip, and now in parallel We'll probably use different shot numbers or something to that effect
885bdf6 to
5a68c38
Compare
mwinkel-dev
left a comment
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.
Re-approving this PR.
f86c68d to
cf5c57d
Compare
|
This is currently in the cmake branch. The gains of adding this with our current jenkins set up is minimal while adding a lot of complexity. This will be merged with cmake. |
First attempt at multithreading the IDL tests
TODO: The write tests still need a way to access mdsip, and now in parallel
We'll probably use different shot numbers or something to that effect
This also moves the
testidvariable out of IDL and turns it into a parameter to each testThis lets us name the threads and output log files for each test individually
TODO: Output a JUnit XML to allow Jenkins to track these tests