-
Notifications
You must be signed in to change notification settings - Fork 183
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: set env SCRAM_ALPAKA_BACKEND for unit tests #9068
Conversation
test parameters:
|
A new Pull Request was created by @smuzaffar for branch IB/CMSSW_14_1_X/master. @smuzaffar, @iarspider, @aandvalenzuela, @cmsbuild can you please review it and eventually sign? Thanks. |
cms-bot internal usage |
please test |
@smuzaffar, would it be possible to use either
? We already have two set of names to handle, I would prefer to avoid introducing a third one 🤷🏻♂️ |
scram knows |
Pull request #9068 was updated. |
please test |
-1 Failed Tests: GpuUnitTests 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: GPU Unit TestsI found 1 errors in the following unit tests: ---> test testTFVisibleDevicesCUDA had ERRORS Comparison SummarySummary:
GPU Comparison SummarySummary:
|
+externals TF gpu unit test is known failure in GPU IBs |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_14_1_X/master IBs (but tests are reportedly failing). This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
New build rules now can set
SCRAM_ALPAKA_BACKEND
env to one of the validalpaka
backends e.gSerialSync, CudaAsync, ROCmAsync
during thescram build runtests
.