[ROOT6] Root update master 20250915#10077
[ROOT6] Root update master 20250915#10077smuzaffar merged 2 commits intocms-sw:IB/CMSSW_16_0_X/rootmasterfrom
Conversation
|
A new Pull Request was created by @akritkbehera for branch IB/CMSSW_16_0_X/rootmaster. @akritkbehera, @cmsbuild, @iarspider, @smuzaffar can you please review it and eventually sign? Thanks. |
|
cms-bot internal usage |
|
Please test |
|
-1 Failed Tests: RelVals AddOn RelValsExpand to see more relval errors ...AddOn Tests |
|
please test |
|
-1 Failed Tests: RelVals AddOn RelValsExpand to see more relval errors ...AddOn Tests |
|
please test with #10079 lets try a debug build of root |
|
testing a possible fix for this failure via cms-sw/root#226 . If successful then we can move to latest root master with which includes root-project/root#19893 |
|
please test with #10079 |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ff4129/48143/summary.html Comparison SummarySummary:
|
|
please test with cms-externals/HLS_arbitrary_Precision_Types#1 for CMSSW_16_0_ROOT6_X |
Would it be okay to change this data member in mutable internal_transient_map_type transientMap_;to a This will probably also speed up the compilation time of CMSSW, because the |
Theoretically maybe. But
template <typename Key, typename T, typename Hash = std::hash<Key>, typename KeyEqual = std::equal_to<Key>,
typename Allocator = tbb::tbb_allocator<std::pair<const Key, T>> >
class concurrent_unordered_mapand they don't provide forward declarations, so forward declaration by us feels brittle (even if the class has an "open specification"). Written that, I wonder if some other way of avoiding TBB header in a header that gets passed to But before doing much I'd like to understand better why we'd have to go though those changes. I have the impression the context is about changing @Dr15Jones Any thoughts? |
It was more by accident. We have avoided including See also: |
|
Pull request #10077 was updated. |
|
please test with #10083 |
|
@guitargeek Thanks for the pointes. I'm still puzzled why (or how) root-project/root#19872 leads to code that uses |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ff4129/48184/summary.html 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: Comparison SummarySummary:
|
|
looks like removing the |
|
I can merge this and trigger ROOT6 IB to see how it behaves with full relvals |
|
+externals |
|
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_16_0_X/rootmaster IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @ftenchini, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
|
I have started an IB for ROOT6 with this change. If we do not see any issues then I guess we do not need root-project/root#19893 |
|
ROOT6 IBs look good, all relvals passed (except the know failures). |
No description provided.