-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
AVXVec: replace 2*insertf128 with 1*_mm256_set_m128d #42446
Conversation
Fixes cms-sw#36542, as suggested by @slava77
please test for CMSSW_13_3_SKYLAKEAVX512_X |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42446/36453
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
please test for CMSSW_13_3_SKYLAKEAVX512_X |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42446/36454
|
A new Pull Request was created by @iarspider for master. It involves the following packages:
@mandrenguyen, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
-1 Failed Tests: Build HeaderConsistency 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: >> Compiling scram_skylake-avx512 /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_13_3_SKYLAKEAVX512_X_2023-07-30-2300/src/DQMServices/Core/src/LegacyIOHelper.cc >> Compiling scram_skylake-avx512 /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_13_3_SKYLAKEAVX512_X_2023-07-30-2300/src/DQMServices/Core/src/MonitorElement.cc >> Compiling scram_skylake-avx512 /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_13_3_SKYLAKEAVX512_X_2023-07-30-2300/src/DQMServices/Core/src/QReport.cc >> Compiling scram_skylake-avx512 /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_13_3_SKYLAKEAVX512_X_2023-07-30-2300/src/DQMServices/Core/src/QTest.cc In file included from /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_13_3_SKYLAKEAVX512_X_2023-07-30-2300/src/DQMServices/Core/src/ROOTFilePB.pb.cc:4: /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_13_3_SKYLAKEAVX512_X_2023-07-30-2300/src/DQMServices/Core/interface/ROOTFilePB.pb.h:12:2: error: #error This file was generated by a newer version of protoc which is 12 | #error This file was generated by a newer version of protoc which is | ^~~~~ /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_13_3_SKYLAKEAVX512_X_2023-07-30-2300/src/DQMServices/Core/interface/ROOTFilePB.pb.h:13:2: error: #error incompatible with your Protocol Buffer headers. Please update 13 | #error incompatible with your Protocol Buffer headers. Please update | ^~~~~ |
please test with cms-sw/cmsdist#8565 for CMSSW_13_3_SKYLAKEAVX512_X |
please test |
-1 Failed Tests: RelVals-INPUT RelVals-INPUTThe relvals timed out after 4 hours. Comparison SummarySummary:
|
@smuzaffar should I restart the relvals job? The compilation (for default release) was successful, as were unit tests (but I don't now if that code is covered by unit tests) |
yes you can restart the relval input job directly via jenkins |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2e2102/34046/summary.html Comparison SummarySummary:
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2e2102/34045/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:
|
There's a lot of failed comparisons, which seems surprising for a fix to a compiler warning. |
@mandrenguyen , please note that #42446 (comment) is for skylake IBs so yes those differences are expected. You should be looking in to #42446 (comment) for production IB comparison |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Fixes #36542, as suggested by @slava77 here
PR validation:
Bot tests