Started by GitHub push by ti-chi-bot[bot]00485664856665715657151.00563556351508ac4e61ec2c23494dc1d51d1bd849d45c67d8dfc1ac4e61ec2c23494dc1d51d1bd849d45c67d8dfc1origin/mainac4e61ec2c23494dc1d51d1bd849d45c67d8dfc1ac4e61ec2c23494dc1d51d1bd849d45c67d8dfc1origin/mainac4e61ec2c23494dc1d51d1bd849d45c67d8dfc1ac4e61ec2c23494dc1d51d1bd849d45c67d8dfc1origin/mainhttps://github.com/PingCAP-QE/ci.gitfalse#15086571550732seed #15081508falsefalse15083445225SUCCESS1773294420498https://do.pingcap.net/jenkins/job/seed/1508/default-9p2smpipelines/pingcap/tiflash/latest/pull_unit_test.groovyac4e61ec2c23494dc1d51d1bd849d45c67d8dfc11773294362000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comfix(tiflash): handle ut-build cache restore in unit test prepare (#4345) ## Summary - make `Unit Test Prepare` resilient when `build_cache_ready` was not initialized before cache restore - detect restored ut-build content by checking `tests/.build/tiflash` inside the cache block - use `mkdir -p tests/.build` to avoid `File exists` failure ## Why In pull_unit_test #5456, `Unit Test Prepare` failed with `mkdir: cannot create directory 'tests/.build': File exists` after cache restore. This change makes the step idempotent and tolerant to cache state mismatches. ## Replay test https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflash%2Fpull_unit_test/detail/pull_unit_test/5461/pipeline/ 2026-03-12 05:46:02 +0000ac4e61ec2c23494dc1d51d1bd849d45c67d8dfc1fix(tiflash): handle ut-build cache restore in unit test prepare (#4345)editpipelines/pingcap/tiflash/latest/pull_unit_test.groovygithttps://do.pingcap.net/jenkins/user/noreplynoreply