-
Notifications
You must be signed in to change notification settings - Fork 184
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
BuildRule: Fix emdplugin cache for multiarch builds #8990
Conversation
A new Pull Request was created by @smuzaffar (Malik Shahzad Muzaffar) for branch IB/CMSSW_14_1_X/master. @smuzaffar, @aandvalenzuela, @iarspider, @cmsbuild can you please review it and eventually sign? Thanks. |
cms-bot internal usage |
test parameters:
|
please test |
please test |
Pull request #8990 was updated. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-674021/37264/summary.html Comparison SummarySummary:
|
+externals |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_14_1_X/master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
We had stopped building cuda/romc backends of alpaka for extra micro-archs of MULTIARCHS/SKYLAKE IBs. Thsi caused runtime issue as the
lib/arch/microarch/.edmplugin
is a symlink tolib/arch/.edmplugin
and CMS FW was trying to load theCudaAsync.so
libs from the ``lib/arch/microarch( as the
lib/arch/microarch/.edmplugin` still had the ref to it). The buildrule update fixes these issue and instead of creaing symlink it now properly creates a separate `.edmplugincache` file for each `lib/arch/microarch/.edmplugin`