Started by GitHub push by ti-chi-bot[bot]00191351913524743247431.006880688015574ce3056a3cb5b524e6fc2bc4efa8a945348d8bbc4ce3056a3cb5b524e6fc2bc4efa8a945348d8bbcorigin/main4ce3056a3cb5b524e6fc2bc4efa8a945348d8bbc4ce3056a3cb5b524e6fc2bc4efa8a945348d8bbcorigin/main4ce3056a3cb5b524e6fc2bc4efa8a945348d8bbc4ce3056a3cb5b524e6fc2bc4efa8a945348d8bbcorigin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#15572474380415seed #15571557falsefalse15573636438FAILURE1775016826806https://do.pingcap.net/jenkins/view/all/job/seed/1557/default-448x0prow-jobs/pingcap/tidb/latest-presubmits.yamlpipelines/pingcap/tidb/latest/pod-ghpr_mysql_test.yamlpipelines/pingcap/tidb/latest/ghpr_mysql_test.groovy4ce3056a3cb5b524e6fc2bc4efa8a945348d8bbc1775016795000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comfeat(pipeline) tidb ghpr_mysql_test job migrate to GCP (#4441) ## Summary Migrate `pingcap/tidb/ghpr_mysql_test` to GCP runtime and mark the job as migrated in prow config. ## Changes 1. Update pipeline structure in `pipelines/pingcap/tidb/latest/ghpr_mysql_test.groovy` - switch to `agent none` + stage-level k8s agents - use `yaml pod_label.withCiLabels(POD_TEMPLATE_FILE, REFS)` instead of `yamlFile` - merge `Checkout` + `Prepare` into `Checkout & Prepare` - keep existing latest job behavior (cache keys / ws cache / post behavior) while applying GCP migration pattern replay build: `https://prow.tidb.net/jenkins/job/pingcap/job/tidb/job/ghpr_mysql_test/2` - result: `SUCCESS` 2026-04-01 04:13:15 +00004ce3056a3cb5b524e6fc2bc4efa8a945348d8bbcfeat(pipeline) tidb ghpr_mysql_test job migrate to GCP (#4441)editpipelines/pingcap/tidb/latest/ghpr_mysql_test.groovyeditprow-jobs/pingcap/tidb/latest-presubmits.yamleditpipelines/pingcap/tidb/latest/pod-ghpr_mysql_test.yamlgithttps://do.pingcap.net/jenkins/user/noreplynoreply