-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
feat(ansible): revert "upgrade for CUDA, TensorRT and CUDNN" #5729
Conversation
This reverts commit 2421b2b.
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
Could we instead check deps fix? #5730 |
The linked PR fixes missing dependencies for arm64 platform. However, without required 0.41.0 release, only nightly build will be valid due to necessary API changes in autoware.universe. I only wonder about linking autoware main branch with autoware.universe latest tagged version. Shouldn't health-check use both autoware and autoware.universe latest tagged version, and health-check-nightly both main branches with making it required workflow check? Otherwise, if any autoware.universe change will require breaking change in autoware, this check will fail. |
First, we revert this. |
@youtalk |
Actually, if we deploy autoware-base by manual trigger with old deps, we don't need to revert PR since container will be build using cached (downgraded) image. Just arm64 fix merge will be needed and later manual trigger of autoware-base after 0.41.0 release. If I'm mistaken, please ignore this comment. |
|
@amadeuszsz Just to confirm, we don't have to revert this one , correct? |
@mitsudome-r |
The base image was changed, so it’s taking time to run the
|
Reverts #5608
It was found that due to the impact of this PR, the build started failing, just like with this job.
https://github.com/autowarefoundation/autoware/actions/runs/13132774294/job/36641359188?pr=5688#step:5:20045
It is necessary to revert it for now.