-
Notifications
You must be signed in to change notification settings - Fork 206
[ROOT6] Update ROOT tip of branch master #8289
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
[ROOT6] Update ROOT tip of branch master #8289
Conversation
|
A new Pull Request was created by @iarspider for branch IB/CMSSW_13_0_X/rootmaster. @cmsbuild, @smuzaffar, @aandvalenzuela, @iarspider can you please review it and eventually sign? Thanks. |
|
test parameters:
|
|
please test |
|
-1 Failed Tests: Build The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: BuildI found compilation error when building: >> Checking EDM Class Transients in libDataFormatsCTPPSDigi.so
@@@@ ----> OK EDM Class Version
>> Checking EDM Class Transients in libDataFormatsBeamSpot.so
@@@@ ----> OK EDM Class Version
>> Checking EDM Class Transients in libDataFormatsCTPPSReco.so
/data/cmsbld/jenkins/workspace/ib-run-pr-tests/testBuildDir/el8_amd64_gcc11/lcg/root/6.29.01-8b1fb99c2f98c5fc80c3d3abd70c9452/etc/cling/std.modulemap:497:10: error: module 'std.bits/uses_allocator_args.h' requires feature 'cplusplus20'
module "bits/uses_allocator_args.h" {
^
/data/cmsbld/jenkins/workspace/ib-run-pr-tests/testBuildDir/el8_amd64_gcc11/external/gcc/11.2.1-f9b9dfdd886f71cd63f5538223d8f161/include/c++/11.2.1/memory_resource:42:10: note: submodule of top-level module 'std' implicitly imported here
#include // uninitialized_construct_using_alloc
^
|
|
@smuzaffar the error is in cmssw code or in root code? Also, there is cling assertion failure logged: |
|
@iarspider , please open a root-project/root issue. Looks like something changes in root whch broke this. I think it might be due to the error mentioned above open a root issue and ping @vgvassilev to look in to it |
|
|
Closing in favor of #8312 |
No description provided.