-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
GPU test does not seem to run in the bot #31878
Comments
A new Issue was created by @jpata Joosep Pata. @Dr15Jones, @dpiparo, @silviodonato, @smuzaffar, @makortel, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign core |
New categories assigned: core @Dr15Jones,@smuzaffar,@makortel you have been requested to review this Pull request/Issue and eventually sign? Thanks |
@jpata , for GPU enabled tested, bot runs two tests
For #31704 bot ran the normal tests but due to a typo in bot did not start the GPU based test. Anyway, this is fixed and there is pending job in jenkins for GPU tests https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/ . Whenever we get hold to a HTCondor GPU resources then the test will start |
Thanks @smuzaffar for the clarification. So in principle the procedure we followed in #31704 should work to also successfully run the CUDA-based tests that run when doing |
bot currently only running GPU based relvals for PRs, In future I will also enable running of unit tests too |
Can this issue be closed? |
yes, seems so, thanks. |
In the PR #31704 I tried to run a basic unit test on the GPU using "please test". However, despite saying "enable gpu" and the test running with "ENABLE_BOT_TESTS = GPU", the test log shows that CUDA was not properly initialized.
I had the same error locally before updating the nvidia driver to the latest 455 version - possibly it's the same problem on the test infrastructure, but I was not able to check.
cc heterogeneous @fwyzard
The text was updated successfully, but these errors were encountered: