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
Fix testRandomService.sh unit test #22231
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22231/3379 |
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages: IOMC/RandomEngine @cmsbuild, @smuzaffar, @Dr15Jones can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@wddgit please take a look. |
This bug fix looks good. The problem was a bug in the test that I put in back in 2013 when I converted the service to support multithreading. Probably I made a mistake when I cut and pasted some test code used for the forking case and did not modify it properly for the multithreading case. The bug was only hit when stream 2 did not process any events. I suppose we never noticed because that did not happen often. It must have been almost never, because I do not remember seeing this unit test ever fail. I'm not sure why stream 2 was not getting events in the new PR test ... Thanks for fixing the bug. |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
If the multistream test doesn't run any event on stream 2, the file
StashStateStream.data_2
is not created. The logic in the test script looks like it should fall back toStashStateStream.data_1
(and..._0
), but the subsequent tests are done againsStashStateFork.data_1
(and..._0
). This PR fixes the unit test by replacing allStashStateFork
withStashStateStream
. I tested that the fix works by manually removing the..._2/1/0
files (within the script).I can only wonder why we haven't seen this case before the PR tests #22069 (where it has failed twice; or maybe we have seen it and it has just been though transient and ignored).
Tested in CMSSW_10_1_X_2018-02-08-2300, no changes expected.