-
Notifications
You must be signed in to change notification settings - Fork 28
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
ROCm 6.0 #321
Comments
Yes it is usually as easy as adding ROCm 6.0 to the cpack matrix + sometimes some tweaks to the docker scripts if the naming convention of the URLs changed. But I probably won’t be able to do this until after the holidays |
Hi @jrmadsen. Just wanted to follow up on this issue and ask if you should already have had a chance to look at the 6.0 update? On our side, we have tried to compile omnitrace with room 6.0 along the lines of what you do in your ci. We used ubuntu 22.04. We ran into two difficulties. The first difficulty concerns It seems the property The second difficulty is that we get a bunch of errors like
It seems it's related to when With these two works, we do get to the |
Hi @maartenarnst, I wasn’t aware of the first issue but I was aware of the second and fixed it in #317. Unfortunately, right now the CI is failing because of some issues with the machines running the CI having issues with our MPI tests. @benrichard-amd is working on fixing that now. Once he’s completed this, we will be able to proceed. Having a new release with ROCm 6.0 seems feasible by the middle of next week. |
OK, thanks for the update. Looking forward to it :) |
Hi there!
Thanks for
Omnitrace
, it's a really nice tool.Any plan for supporting
ROcm 6.0
? Is it as simple as adding it to yourcpack
action matrix or do we need more?Thanks!
(@maartenarnst will be interested)
The text was updated successfully, but these errors were encountered: