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
Remove confusing message #13018
Remove confusing message #13018
Conversation
When CMSSW was single-threaded, the following message from the signal handler made sense: ``` NOTE:The first few functions on the stack are artifacts of processing the signal and can be ignored ``` This is no longer true! You have to pick through the contents of each thread's stack.
Retains the prior whitespace.
A new Pull Request was created by @bbockelm (Brian Bockelman) for CMSSW_8_0_X. It involves the following packages: FWCore/Services @cmsbuild, @smuzaffar, @Dr15Jones, @davidlange6 can you please review it and eventually sign? Thanks. Following commands in first line of a comment are recognized
|
Crap. I used github's in-browser editor and this (for reasons unknown to me) decided to create the branch in the |
please test |
The tests are being triggered in jenkins. |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
When CMSSW was single-threaded, the following message from the signal handler made sense:
This is no longer true! You have to pick through the contents of each thread's stack.