-
Notifications
You must be signed in to change notification settings - Fork 206
[ROOT636] Updated root to tip of branch v6-36-00-patches #10111
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
[ROOT636] Updated root to tip of branch v6-36-00-patches #10111
Conversation
|
A new Pull Request was created by @akritkbehera for branch IB/CMSSW_16_0_X/root636. @akritkbehera, @cmsbuild, @iarspider, @smuzaffar can you please review it and eventually sign? Thanks. |
|
cms-bot internal usage |
|
Please test |
|
-1 Failed Tests: UnitTests Unit TestsI found 1 errors in the following unit tests: ---> test testFWCoreFWLite had ERRORS Comparison SummarySummary:
|
|
Test parameters:
|
|
Please test |
|
-1 Failed Tests: UnitTests Unit TestsI found 2 errors in the following unit tests: ---> test testFWCoreFWLite had ERRORS ---> test TestGeneratorInterfacePythia8ConcurrentGeneratorFilter had ERRORS Comparison SummarySummary:
|
|
please test with cms-sw/cmssw#49103 for CMSSW_16_0_ROOT636_X |
|
@makortel , we have not updated root636 for last few weeks, so I will suggest to get this in ROOT636 IBs and debug the unit test failure in the IB. Though cms-sw/cmssw#49103 fixes the unit test for root 636 but we have clang build errors , I guess we can address that failure in the cms-sw/cmssw#49103 . Merge this in IB we allow us to test latest ROOT 636 changes on bit large scale ( full threaded relvals in IBs) |
|
+externals though there is a unit test failure but we can look in to that via cms-sw/cmssw#49103 |
|
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_16_0_X/root636 IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @ftenchini, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
No description provided.