Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Run the Dumpling GitHub Actions workflow. Its download binary dependencies step invokes sh dumpling/install.sh, which downloads MinIO and the MinIO client (mc) from retired endpoints.
The dependency failure can also be reproduced without building TiDB:
curl --fail --head https://dl.min.io/server/minio/release/linux-amd64/minio
curl --fail --head https://dl.minio.io/client/mc/release/linux-amd64/mc
Both endpoints returned HTTP 410 on 2026-09-17.
Evidence:
2. What did you expect to see? (Required)
The CI dependencies download successfully, allowing TiDB/Lightning builds and Dumpling integration tests to run.
3. What did you see instead (Required)
The job exits during dependency setup, before compiling TiDB or running integration tests:
2026-09-17T03:39:14Z https://dl.min.io/server/minio/release/linux-amd64/minio
HTTP request sent, awaiting response... 410 Gone
ERROR 410: Gone.
Process completed with exit code 8.
dumpling/install.sh exits on the server download failure. Its subsequent mc download uses another endpoint that also returns HTTP 410, so replacing only the server URL is insufficient.
The download service's response states that the archived community projects' binaries and hotfix builds are no longer served. This is an external CI dependency breakage, not a failure of PR #71208's SQL or HTTP behavior. Both downloads need an available, pinned source; retries against the retired endpoints do not address the cause.
4. What is your TiDB version? (Required)
Dumpling CI for the master branch. The linked failing job checked out merge commit 4b6b400b91e0b8ee60d77f4f20e97fd22b512ce8, combining PR head a00d464e36070e721e144fe4481d66dc70a5e21c with base 02e5d7b3ecf7615dfdfc238b272f39409bbd55f1.
No SELECT tidb_version() output is available because the job fails before TiDB is built or started.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Run the Dumpling GitHub Actions workflow. Its
download binary dependenciesstep invokessh dumpling/install.sh, which downloads MinIO and the MinIO client (mc) from retired endpoints.The dependency failure can also be reproduced without building TiDB:
Both endpoints returned HTTP 410 on 2026-09-17.
Evidence:
2. What did you expect to see? (Required)
The CI dependencies download successfully, allowing TiDB/Lightning builds and Dumpling integration tests to run.
3. What did you see instead (Required)
The job exits during dependency setup, before compiling TiDB or running integration tests:
dumpling/install.shexits on the server download failure. Its subsequentmcdownload uses another endpoint that also returns HTTP 410, so replacing only the server URL is insufficient.The download service's response states that the archived community projects' binaries and hotfix builds are no longer served. This is an external CI dependency breakage, not a failure of PR #71208's SQL or HTTP behavior. Both downloads need an available, pinned source; retries against the retired endpoints do not address the cause.
4. What is your TiDB version? (Required)
Dumpling CI for the
masterbranch. The linked failing job checked out merge commit4b6b400b91e0b8ee60d77f4f20e97fd22b512ce8, combining PR heada00d464e36070e721e144fe4481d66dc70a5e21cwith base02e5d7b3ecf7615dfdfc238b272f39409bbd55f1.No
SELECT tidb_version()output is available because the job fails before TiDB is built or started.