-
Notifications
You must be signed in to change notification settings - Fork 34
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
WIP switch GPU workers to image that uses multi engine generic worker #700
base: main
Are you sure you want to change the base?
Conversation
cf39689
to
ea4c6ae
Compare
It looks like these new workers largely work fine. We are hitting taskcluster/taskcluster#7128, which will need to be fixed before this is landable, but all of the GPU tasks seem to work well within Docker on this new image. |
109dade
to
44827e9
Compare
taskcluster/taskcluster#7428 has this patch. We'll need a new worker image when that's done to pick it up. I also want to wait on mozilla-releng/fxci-config#244 to land to avoid some unnecessary confusion in this repo. |
26b3d9b
to
996ab9e
Compare
The new image we're upgrading GPU workers to uses Ubuntu 24.04, which makes it incompatible with various parts of the pipeline (mostly due to Python package pinning). As it turns out, the easiest way to fix this is to dockerize the GPU tasks. We need slight updates to GPU task payloads to accommodate this. This will fix mozilla#391.
Without this we end up with these files being inaccessible in subsequent tasks.
This has always been needed, but it was found on the host system on the previous image.
7792ffc
to
a111917
Compare
…GPU workers And also, use the newly minted dated image for them, which appears to be working well in mozilla/translations#700.
…GPU workers And also, use the newly minted dated image for them, which appears to be working well in mozilla/translations#700.
This will be necessary for #466 due to the "simple" engine not supporting chain of trust.
This initial work is just for some sanity checking that nothing obvious breaks. Aside from tasks in automation, we also need to see how interactive tasks behave, and if they meet the needs (most notably, see if we can have root in interactive tasks if needed).