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
Make unit test fail immediately if one of the cmsRun commands fail #68
Conversation
On the one hand -e would immediately stop the script and takes less code (2 characters), which is good. On the other hand, the way it is done prints out helpful info into the log that says exactly what command and configuration failed. I was also copying a pattern in these test shell scripts which has been around longer than I have which I have copied many times before. I do not know who started it. |
Ok... I guess we should clean up all our scripts to always run with -e ... Merging this for now. |
Make unit test fail immediately if one of the cmsRun commands fail
Identifies the prs that went into the branch from a merge commit
Check that the decay postfix is conforming
Updated to cmg-central; some conflicts resolved
Thanks Giovanni and all
Read basic cut-based muon ID from standard selectors
Customize to the unit tests that fail due to old input samples
Update ntuplizer and sample to the latest pre-release
Co-authored-by: Anders <aryd@cern.ch>
Update to l1t-phase2-v3.3.39 tag
No description provided.