Skip to content
Started 19 days ago
Took 19 min

Build #340 (Apr 29, 2024, 9:22:46 AM)

PR #10883: kvClient (ticdc): resolve stale lock more aggressively to reduce resolvedTs lag (#10855) https://github.com/pingcap/tiflow/pull/10883
Build Artifacts
log-G04.tar.gz7.51 MB view
Changes
  1. fix(br): use failpoint tidb-server instead (#2936) (commit: b270b7a) (details / githubweb)
  2. fix(scripts/pingcap): fix script of adding version placeholder (#2937) (commit: a0bb344) (details / githubweb)
  3. chore(tiflash): update tiflash new merged ut (#2938) (commit: c944560) (details / githubweb)
  4. feat: tikv new ut add trigger on 6.1 (#2940) (commit: 09f9a72) (details / githubweb)
  5. fix: upadte new ut on tikv 6.1 (#2939) (commit: 7c92534) (details / githubweb)
  6. feat(scripts/aritfacts): add scripts to check internal images (#2941) (commit: 094391f) (details / githubweb)
  7. chore(deps): update dependency idna to v3.7 (#2931) (commit: 618760b) (details / githubweb)
  8. feat(tidb): test flashbacktest package (#2942) (commit: cb9bc9e) (details / githubweb)
  9. feat: enable report and trigger on tiflash master new pipeline (#2943) (commit: 746b6a2) (details / githubweb)
  10. fix(pingcap/ng-monitoring): fix the base_ref arg for create pull request on pingcap/monitoring (#2945) (commit: bd5d20b) (details / githubweb)
  11. chore(tiflash): retry only after get src code cache from ks3 (#2946) (commit: faae7c0) (details / githubweb)
  12. feat: disable old pipeline trigger on tiflash master (#2944) (commit: 8c60e55) (details / githubweb)

Started by user Jenkins Admin

This run spent:

  • 17 min waiting;
  • 19 min build duration;
  • 19 min total from scheduled to completion.
Revision: 8c60e558a9356c5a25645eebaade802e946e45b6
Repository: https://github.com/PingCAP-QE/ci
  • main
The following steps that have been detected may have insecure interpolation of sensitive variables (click here for an explanation):
  • httpRequest: [token]
  • httpRequest: [token]

Identified problems

No identified problem

No problems were identified. If you know why this problem occurred, please add a suitable Cause in https://pingcap.feishu.cn/wiki/wikcno79XYpVsvJeiRsMm38b5eh, add a config it.