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
Updated root to tip of branch v6-14-00-patches #4277
Updated root to tip of branch v6-14-00-patches #4277
Conversation
A new Pull Request was created by @mrodozov (Mircho Rodozov) for branch IB/CMSSW_10_3_X/rootnext. @cmsbuild, @smuzaffar, @gudrutis, @mrodozov can you please review it and eventually sign? Thanks. |
please test |
The tests are being triggered in jenkins. |
abort |
Jenkins tests are aborted. |
The tests are being triggered in jenkins. |
please test |
The tests are being triggered in jenkins. |
test on it's own to see if it would break as master (still one unit test and addon test failing) |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 37a12df You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests AddOn
I found errors in the following unit tests: ---> test runtestPhysicsToolsPatAlgos had ERRORS
I found errors in the following addon tests: cmsDriver.py RelVal -s HLT:PRef,RAW2DIGI,L1Reco,RECO --data --scenario=pp -n 10 --conditions auto:run2_data_PRef --relval 9000,50 --datatier "RAW-HLT-RECO" --eventcontent FEVTDEBUGHLT --customise=HLTrigger/Configuration/CustomConfigs.L1THLT --era Run2_2018 --processName=HLTRECO --filein file:RelVal_Raw_PRef_DATA.root --fileout file:RelVal_Raw_PRef_DATA_HLT_RECO.root : FAILED - time: date Fri Aug 24 21:25:35 2018-date Fri Aug 24 20:58:52 2018 s - exit: 35584 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@mrodozov |
Compared with what we merged on root master branch is acceptable. So I'll merge it |
+externals |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_10_3_X/rootnext IBs (but tests are reportedly failing). 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) |
IIUC, this PR is now included in CMSSW_10_3_ROOT614_X_2018-08-28-2300, including the fix from root-project/root#2488 I still have a similar problem to the one that was present in earlier tests in July in cms-sw/cmssw#22594 (comment) To reproduce
The above ends with
in CMSSW_10_3_0_pre2 the same leads to some meaningful printouts
@smuzaffar, @mrodozov please check/confirm that CMSSW_10_3_ROOT614_X_2018-08-28-2300, includes new root build with the fix from root-project/root#2488 |
it looks like the new root build is not included:
|
oops, sorry for the noise in the last message, I was in a wrong window. The CMSSW_10_3_ROOT614_X_2018-08-28-2300 has root from |
the stack trace is different from what I've see in July
@pcanal please check if you can reproduce the problem I mentioned above #4277 (comment) |
Get latest commits (recent PR root-project/root#2488 now merged)