ROCmSoftwarePlatform
Test jenkins CI
retest this please: this triggered http://rocmhead.amd.com:8080/job/pytorch/job/pytorch-ci/237 which used ${sha1} as "Branch Specifier" in SCM configuration
then triggered http://rocmhead.amd.com:8080/job/pytorch/job/pytorch-ci/238 which used ${ghprbActualCommit} as "Branch Specifier" in SCM configuration
then triggered http://rocmhead.amd.com:8080/job/pytorch/job/pytorch-ci/239 which set "Custom user name/e-mail address" in "Additional Behaviours" in SCM configuration so that we can get around the "Please tell me who you are." error in previous build
then triggered (as sub-job) http://rocmhead.amd.com:8080/job/pytorch/job/pytorch-build/230 which removed "${sha1}" as "Branch Specifier" in SCM configuration for pytorch-build CI job
retest this please: trying out NODE_LABEL and EXTENSION_BUILD_GFXARCH parameters set to gfx90a to see if it triggers builds on MI200
retest this please:
- http://rocmhead.amd.com:8080/job/pytorch/job/pytorch-ci/301/ Removed "pass-through git commit that was built": pytorch-ci-scripts-download failed due to no space on the machine; pytorch-build had no merge and failed due to no artifacts from the previous sub-job.
Changed "Branches to build" to ${ghprbActualCommit} in pytorch-build sub-job configuration
- http://rocmhead.amd.com:8080/job/pytorch/job/pytorch-ci/302/ pytorch-ci-scripts-download failed due to no space on the same machine (ixt-rack-158); pytorch-build had successful merge and failed due to no artifacts from the previous sub-job.
Temporarily disabled ixt-rack-158 node in Jenkins
-
http://rocmhead.amd.com:8080/job/pytorch/job/pytorch-ci/303/ pytorch-build had successful merge but build stuck after "Exporting S3 test stats to .pytorch-test-times.json"
-
Investigated a non-test build (http://rocmhead.amd.com:8080/job/pytorch/job/pytorch-ci/304/). Found "Please tell me who you are." error mentioned above. Added "Custom user name/e-mail address" in "Additional Behaviours" in SCM configuration in pytorch-build sub-job
