-
Notifications
You must be signed in to change notification settings - Fork 4.6k
[16_0_X] Improve PortableHost{Collection,Object} dictionary declarations
#49774
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
base: CMSSW_16_0_X
Are you sure you want to change the base?
[16_0_X] Improve PortableHost{Collection,Object} dictionary declarations
#49774
Conversation
…heir aliased types in classes_def.xml In ROOT presently the type alias gets listed in the rootmap file only if the alias is requested before the real type. Having the type alias in the rootmap file is necessary to avoid header parsing for the execution of the read rules that use the type alias names.
…aliased-to types This should avoid ROOT header parsing
They are not in DataFormats, so they are allowed to be transient only.
|
A new Pull Request was created by @makortel for CMSSW_16_0_X. It involves the following packages:
@Moanwar, @civanch, @cmsbuild, @fwyzard, @jfernan2, @kpedro88, @makortel, @mandrenguyen, @mdhildreth, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
cms-bot internal usage |
|
enable gpu |
|
@cmsbuild, please test |
|
-1 Size: This PR adds an extra 20KB to repository Comparison SummarySummary:
AMD_MI300X Comparison SummarySummary:
AMD_W7900 Comparison SummarySummary:
NVIDIA_L40S Comparison SummarySummary:
NVIDIA_T4 Comparison SummarySummary:
|
|
On NVIDIA H100 some of the workflows failed with The symptoms look like #47270 with |
|
+heterogeneous |
|
The failing tests were running on while the passing ones ran on @smuzaffar do we have different runners for the H100 tests ? |
|
ignore tests-rejected with external-failure |
PR description:
Backport of #48824. Original description
PR validation:
None beyond #48824
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Backport of #48824 (using the same branch).