-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Hcal Phase I #2265
Hcal Phase I #2265
Conversation
ianna
commented
Feb 2, 2014
- Merging all branches
- Fix from Sunanda for Phase I
…y are taken from Hcal numbering now.
A new Pull Request was created by @ianna for CMSSW_6_2_X_SLHC. Hcal Phase I It involves the following packages: CalibCalorimetry/CaloMiscalibTools @diguida, @deguio, @lveldere, @ianna, @anton-a, @thspeer, @rcastello, @civanch, @ojeda, @cmsbuild, @ktf, @Dr15Jones, @mdhildreth, @rovere, @giamman, @slava77, @ggovi, @Degano, @mulhearn, @apfeiffer1, @nclopezo, @danduggan can you please review it and eventually sign? Thanks. |
+1 tested with
all steps pass. |
Full test suite still running, but testing the GEMs with
fails when customising:
I'll report on the other tests when they're finished. |
@mark-grimes - customisations are not needed for Hcal.
should be removed from where it is defned. |
@mark-grimes - this should fix the 3400 workflow. @salavat - could you, please, check customisations for Hcal? I think, I've removed everything unneeded. |
Pull request #2265 was updated. @diguida, @deguio, @lveldere, @ianna, @anton-a, @thspeer, @rcastello, @civanch, @ojeda, @cmsbuild, @ktf, @Dr15Jones, @mdhildreth, @rovere, @giamman, @slava77, @ggovi, @Degano, @mulhearn, @apfeiffer1, @nclopezo, @danduggan can you please check and sign again. |
Pull request #2265 was updated. @diguida, @deguio, @lveldere, @ianna, @anton-a, @thspeer, @rcastello, @civanch, @ojeda, @cmsbuild, @ktf, @Dr15Jones, @mdhildreth, @rovere, @giamman, @slava77, @ggovi, @Degano, @mulhearn, @apfeiffer1, @nclopezo, @danduggan can you please check and sign again. |
+1 |
1 similar comment
+1 |
This fixes the configuration problem (3400, 4400, 4500, 4502 and 15001 also failed before this fix). Now 3400 and 15001 fail in harvesting with:
Note that there are several of these messages in the log:
3400 when running with combinedCustoms.cust_2019WithGem crashes in harvesting with the following stack trace:
|
Pull request #2265 was updated. @diguida, @deguio, @lveldere, @ianna, @anton-a, @thspeer, @rcastello, @civanch, @ojeda, @cmsbuild, @ktf, @Dr15Jones, @mdhildreth, @rovere, @giamman, @slava77, @ggovi, @Degano, @mulhearn, @apfeiffer1, @nclopezo, @danduggan can you please check and sign again. |
@mark-grimes - strange, the following command runs fine for me:
|
+1 |
Tried again with the updated pull request. The GEM test (as in @ianna's comment above) now runs fine but still get the same errors in harvesting for tests 3400 and 15001. |
@mark-grimes - is it step4 your talking about? |
@ianna Yes, step 4 for both 3400 and 15001. Tests 3300, 4100, 4400, 40001, 50002, 60002, 60001, 4502, 4500, 5001, and 50001 run fine all the way through. |
@mark-grimes - I guess, the errors come when you do not have additional (correct?) customize option. Harvesting fails due to collection name mismatch which is defined in customization fragments for all other steps. Customization of step4 does not include "--customise SLHCUpgradeSimulations/Configuration/combinedCustoms.cust_2019" as the other steps do, there is only tracker customization.
|
@mark-grimes - correction - hcal conditions mismatch |
-1 ---> test runtestPhysicsToolsPatAlgos had ERRORS you can see the results of the tests here: |
@cmsbuild - the test which fails is not applicable to SLHC. It test LHC startup scenario: |
merge @ianna yes, harvesting only has the tracking customisations. Tried step4 of 3400 with the full customisation and it ran through. |
did we then update 3400 to have the full customization in step4? (this can be generally fixed I guess - indeed was a problem before) On Feb 4, 2014, at 11:36 AM, Mark Grimes notifications@github.com
|
@davidlange6 - or we see if Hcal relabeling settings can be moved out. I'll check it when the new IB is ready. |