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
bugfix for sherpa compiled with openmpi support #20401
Conversation
The code-checks are being triggered in jenkins. |
A new Pull Request was created by @pmillet for master. It involves the following packages: GeneratorInterface/SherpaInterface @cmsbuild, @efeyazgan, @perrozzi, @thuer, @govoni can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/PR-20401/525 Code check has found code style and quality issues which could be resolved by applying a patch in https://cmssdt.cern.ch/SDT/code-checks/PR-20401/525/git-diff.patch You can run |
@pmillet please apply the suggested patch https://cmssdt.cern.ch/SDT/code-checks/PR-20401/525/git-diff.patch and commit/push again |
The code-checks are being triggered in jenkins. |
+code-checks |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 366c7b8 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: Build ClangBuild
I found an error when building: /cvmfs/cms-ib.cern.ch/nweek-02488/slc6_amd64_gcc630/external/thepeg/2.0.4-ghjeda4/include/ThePEG/Pointer/RCPtr.h: In instantiation of 'ThePEG::Pointer::RCPtr& ThePEG::Pointer::RCPtr::create(ThePEG::Pointer::RCPtr::const_reference) [with T = ThePEG::LesHouchesInterface; ThePEG::Pointer::RCPtr::const_reference = const ThePEG::LesHouchesInterface&]': /cvmfs/cms-ib.cern.ch/nweek-02488/slc6_amd64_gcc630/external/thepeg/2.0.4-ghjeda4/include/ThePEG/Pointer/RCPtr.h:126:22: required from 'static ThePEG::Pointer::RCPtr ThePEG::Pointer::RCPtr::Create(ThePEG::Pointer::RCPtr::const_reference) [with T = ThePEG::LesHouchesInterface; ThePEG::Pointer::RCPtr::const_reference = const ThePEG::LesHouchesInterface&]' /cvmfs/cms-ib.cern.ch/nweek-02488/slc6_amd64_gcc630/external/thepeg/2.0.4-ghjeda4/include/ThePEG/Pointer/RCPtr.h:869:69: required from 'static ThePEG::Pointer::PtrTraits >::pointer ThePEG::Pointer::PtrTraits >::create(ThePEG::Pointer::PtrTraits >::const_reference) [with T = ThePEG::LesHouchesInterface; ThePEG::Pointer::PtrTraits >::pointer = ThePEG::Pointer::RCPtr; ThePEG::Pointer::PtrTraits >::const_reference = const ThePEG::LesHouchesInterface&]' /cvmfs/cms-ib.cern.ch/nweek-02488/slc6_amd64_gcc630/external/thepeg/2.0.4-ghjeda4/include/ThePEG/Pointer/PtrTraits.h:204:55: required from 'typename ThePEG::Pointer::Ptr::pointer ThePEG::Pointer::new_ptr(const T&) [with T = ThePEG::LesHouchesInterface; typename ThePEG::Pointer::Ptr::pointer = ThePEG::Pointer::RCPtr]' /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-09-05-2300/src/GeneratorInterface/ThePEGInterface/plugins/ThePEGLesHouchesInterface.cc:38:53: required from here /cvmfs/cms-ib.cern.ch/nweek-02488/slc6_amd64_gcc630/external/thepeg/2.0.4-ghjeda4/include/ThePEG/Pointer/RCPtr.h:147:11: error: invalid new-expression of abstract class type 'ThePEG::LesHouchesInterface' ptr = new T(t); ^~~~~~~~ /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-09-05-2300/src/GeneratorInterface/ThePEGInterface/plugins/ThePEGLesHouchesInterface.cc:30:7: note: because the following virtual functions are pure within 'ThePEG::LesHouchesInterface': class LesHouchesInterface : public LesHouchesReader { ^~~~~~~~~~~~~~~~~~~
I found a compilation error while trying to compile with clang: >> Compiling /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-09-05-2300/src/DataFormats/Common/src/PtrVectorBase.cc >> Compiling /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-09-05-2300/src/DataFormats/Common/src/ThinnedAssociation.cc In file included from /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_3_X_2017-09-05-2300/src/GeneratorInterface/ThePEGInterface/src/ThePEGInterface.cc:22: In file included from /cvmfs/cms-ib.cern.ch/nweek-02488/slc6_amd64_gcc630/external/thepeg/2.0.4-ghjeda4/include/ThePEG/Repository/Repository.h:16: In file included from /cvmfs/cms-ib.cern.ch/nweek-02488/slc6_amd64_gcc630/external/thepeg/2.0.4-ghjeda4/include/ThePEG/PDT/ParticleData.h:19: /cvmfs/cms-ib.cern.ch/nweek-02488/slc6_amd64_gcc630/external/thepeg/2.0.4-ghjeda4/include/ThePEG/Utilities/Selector.h:131:50: error: ISO C++1z does not allow dynamic exception specifications [-Wdynamic-exception-spec] T & select(double rnd, double * remainder = 0) throw(range_error); ^~~~~~~~~~~~~~~~~~ /cvmfs/cms-ib.cern.ch/nweek-02488/slc6_amd64_gcc630/external/thepeg/2.0.4-ghjeda4/include/ThePEG/Utilities/Selector.h:131:50: note: use 'noexcept(false)' instead T & select(double rnd, double * remainder = 0) throw(range_error); ^~~~~~~~~~~~~~~~~~ The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison not run due to Build errors (RelVals and Igprof tests were also skipped) |
The tests are being triggered in jenkins. |
+1 Tested at: 366c7b8
The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: RelVals
When I ran the RelVals I found an error in the following worklfows: runTheMatrix-results/534.0_sherpa_ZtoEE_0j_OpenLoops_13TeV_MASTER+sherpa_ZtoEE_0j_OpenLoops_13TeV_MASTER+HARVESTGEN/step1_sherpa_ZtoEE_0j_OpenLoops_13TeV_MASTER+sherpa_ZtoEE_0j_OpenLoops_13TeV_MASTER+HARVESTGEN.log The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped) |
So if I read the log correctly we are back to the gcc incompatibility error as expected. I will update the relval samples for gcc630. Library_Loader::LoadLibrary(): /build/cmsbld/jenkins-workarea/workspace/ib-any-integration/runTheMatrix-results/534.0_sherpa_ZtoEE_0j_OpenLoops_13TeV_MASTER+sherpa_ZtoEE_0j_OpenLoops_13TeV_MASTER+HARVESTGEN/Process/Amegic/lib/libProc_fsrchannels2.so: undefined symbol: _ZN6PHASIC14Single_Channel4NameEv
Library_Loader::LoadLibrary(): Failed to load library 'libProc_fsrchannels2.so'. |
@efeyazgan, @perrozzi, @thuer, @govoni @davidlange6 - anything preventing this from being included? its needed for Sherpa to work with cms-sw/cmsdist#3405 (merged) |
+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 (and backports should be raised in the release meeting by the corresponding L2) |
I was actually waiting for #20515 to be merged in order to re-run the tests. From the pure GEN point of view this is good to go, approved. |
@@ -66,7 +69,7 @@ class SherpaHadronizer : public gen::BaseHadronizer { | |||
edm::ParameterSet SherpaParameterSet; | |||
unsigned int maxEventsToPrint; | |||
std::vector<std::string> arguments; | |||
SHERPA::Sherpa Generator; | |||
SHERPA::Sherpa *Generator = new SHERPA::Sherpa(); |
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.
hi @pmillet - please make this a smart pointer.
isInitialized=false; | ||
//initialization of Sherpa moved to initializeForInternalPartons | ||
} | ||
|
||
SherpaHadronizer::~SherpaHadronizer() | ||
{ | ||
Generator->~Sherpa(); | ||
#ifdef USING__MPI | ||
MPI::Finalize(); |
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.
so this is a sign that you can not use the default CMSSW builds.. have you considered run time switches to provide this same functionality?
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.
@davidlange6 -
sherpa is either compiled with or without mpi support, so runtime switches are not an option
if it is compiled with mpi support it needs the mpi init and finalize calls even if it is not
parallelized using mpi (this is the case here)
merge |
No description provided.