Conversation
|
/azp run ONNX Runtime Web CI Pipeline |
|
Azure Pipelines successfully started running 1 pipeline(s). |
snnn
force-pushed
the
snnn/ci
branch
2 times, most recently
from
ac77f27 to
9333122
Compare
snnn
changed the title
|
I bet: if I find a time when nobody uses this pipeline to submit this PR, then everything will pass. |
snnn
changed the title
|
/azp run Linux GPU CI Pipeline, Linux MIGraphX CI Pipeline |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
The pipeline uses current user ID to run docker (and the user id might not exists in docker image): How does BUILD_UID=1004 help? |
I bet the UID is always 1004. I added two commands at: In the log it shows the uid is 1004. And the /home/onnxruntimedev folder is owned by the onnxruntimedev user, so, in theory it should work. But it is not working. When we built the image, we have:
|
Shall we also add group id using |
|
/azp run Linux GPU CI Pipeline, Linux MIGraphX CI Pipeline |
|
Azure Pipelines successfully started running 2 pipeline(s). |
### Description Set build user's uid when creating Migraphx/ROCM docker images
### Description Set build user's uid when creating Migraphx/ROCM docker images
4 participants
Description
Set build user's uid when creating Migraphx/ROCM docker images
Motivation and Context
The two pipelines have a serious issue: the docker image used for building/testing the code could come from any branch! Because the machine has 8 GPUs. We don't want to waste the GPUs, so we run multiple ADO agents there to run build pipelines in parallel. However, there is only one docker daemon.
Therefore, last time when I made a change to the ROCM pipeline's docker image I made an error there but I still saw the pipeline passed. Then, later on after I checked in the change the pipeline started failing. It is a chaos.
This PR couldn't address the fundamental issue. It just fixes the mistake I introduced.