Hi Konstantin, I just checked the Google Cloud incidents and it appears that there was a problem affecting VMs in us-central1 where our pods are running. The incident timeline: * Started on October 13, 2026 at 3:19:12 PM UTC+1 * Resolved on October 13, 2026 at 6:35:59 PM UTC+1
At the moment, I see 61 pods up and running normally for the following PRs: 6644, 6815, 6872. Let's see if the problem persists to investigate further. Best, Stamatis On Wed, Oct 14, 2026 at 12:48 AM Konstantin Bereznyakov <[email protected]> wrote: > > Hi all, > > I investigated repeated CI failures on HIVE-30037 (PR #6842 > (https://github.com/apache/hive/pull/6842)) and found matching > agent/pod failures on unrelated PRs. > > All times below are October 13, UTC: > > #6842 build #12: split-09 pod failed at 09:24; postprocessing raised > AgentOfflineException. Archived test reports contain zero > failures/errors, including the new branch tests. > PR #6861 (https://github.com/apache/hive/pull/6861), build #8: > split-15 pod failed at 16:58. > PR #6871 (https://github.com/apache/hive/pull/6871), build #3: six > pods failed between 18:58 and 19:17. > #6842 build #13: pod failed at 19:28 during workspace upload, after > successful compilation and before testing. > > The logs consistently show ChannelClosedException, “Pod just failed,” > and agent deletion. This appears to be a shared infrastructure issue. > > Could someone with CI access check the Kubernetes pod/node events? I > have saved all four console logs. > > Thanks, > Konstantin
