Skip to content

Fix init time logic to ensure that time is not initiated‌ when the last cache will not updated during the execution phase #13138

Fix init time logic to ensure that time is not initiated‌ when the last cache will not updated during the execution phase

Fix init time logic to ensure that time is not initiated‌ when the last cache will not updated during the execution phase #13138

Triggered via pull request January 28, 2026 02:46
@Wei-hao-LiWei-hao-Li
synchronize #17094
fixInit
Status Cancelled
Total duration 17m 19s
Artifacts

table-cluster-it-1c1d.yml

on: pull_request
Matrix: Simple
Fit to window
Zoom out
Zoom in

Annotations

5 errors
Simple (ubuntu-latest)
Canceling since a higher priority waiting request for Table Cluster IT - 1C1D-refs/pull/17094/merge exists
Simple (ubuntu-latest)
The operation was canceled.
Simple (windows-latest)
Canceling since a higher priority waiting request for Table Cluster IT - 1C1D-refs/pull/17094/merge exists
Simple (windows-latest)
The operation was canceled.
Table Cluster IT - 1C1D
Canceling since a higher priority waiting request for Table Cluster IT - 1C1D-refs/pull/17094/merge exists