Started by GitHub push by ti-chi-bot[bot]009975997558467584671.019489194890779569512951210230f857cb0df87cf37ac5c37f4d2e5251feea293690f857cb0df87cf37ac5c37f4d2e5251feea29369origin/main0f857cb0df87cf37ac5c37f4d2e5251feea293690f857cb0df87cf37ac5c37f4d2e5251feea29369origin/main0f857cb0df87cf37ac5c37f4d2e5251feea293690f857cb0df87cf37ac5c37f4d2e5251feea29369origin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1023/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1023/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1023/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1023/testsfalse#10235846783303seed #10231023falsefalse10231981027SUCCESS1758275466571https://do.pingcap.net/jenkins/view/all/job/seed/1023/default-ngjzjpipelines/pingcap/tidb/latest/pull_br_integration_test.groovy0f857cb0df87cf37ac5c37f4d2e5251feea293691758275443000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comfix: increase tidb br integration test timeout duration (#3753) The pass rate of the tidb BR integration test (pull_br_integration_test) is relatively low, and a large number of builds fail due to timeout. Analysis of Jenkins logs reveals the following: 1. The test is forcibly terminated by the SIGTERM signal during execution (exit code 143). 2. The current timeout configuration is insufficient: total timeout is 60 minutes, and the timeout for a single test group is 45 minutes. Adjust the timeout configuration as follows: 1. Total timeout: increased from 60 minutes to 90 minutes. 2. Test group timeout: increased from 45 minutes to 60 minutes. 2025-09-19 09:50:43 +00000f857cb0df87cf37ac5c37f4d2e5251feea29369fix: increase tidb br integration test timeout duration (#3753)editpipelines/pingcap/tidb/latest/pull_br_integration_test.groovygithttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply