ci(temporal-conformance): 两个 skewed-zone 测试步骤挂上 run-with-stall-guard (#4331) - #4335
Merged
Merged
Conversation
…h-stall-guard (#4331) The two Temporal Conformance test legs still ran bare after #4298 gave Test Core the stall guard, so a mid-suite stall burned the full 30-minute job timeout and ended as an uninformative "The operation was canceled" (#4331: once frozen mid-file in core's kernel.test, once silent for 24 minutes after every suite printed Done). Same wiring and parameters as Test Core: silence past 10 minutes becomes a labeled red naming the last output line, and the guard's process-group kill covers the refused-to-exit shape too. The zone-assert node -e lines stay outside the wrapper — a one-shot print cannot stall. Closes #4331 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HXjVcohpYTsZY7D5p91dJQ
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HXjVcohpYTsZY7D5p91dJQ
github-actions
Bot
added
documentation
os-zhuang
marked this pull request as ready for review
July 31, 2026 06:51
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
变更内容
#4298 给 Test Core 挂上
scripts/run-with-stall-guard.mjs之后,Temporal Conformance (live PG + MySQL) 的两个测试步骤仍在裸跑,#4331 实测了后果:mid-suite stall 每次烧满 30 分钟 job 超时,以毫无信息量的「The operation was canceled」收场。本 PR 给这两个步骤包上与 Test Core 完全相同的 guard 接线:Run driver-sql suite against both live serversRun the non-SQL temporal backends under the skewed process zone均为
node scripts/run-with-stall-guard.mjs --log "$RUNNER_TEMP/<leg>.log" --stall-minutes 10 -- …(与 Test Core 同参数)。说明
Done后零输出 24 分钟、进程不退出)都会在静默 10 分钟后转成带「last line」标注的快速失败;guard 的 process-group kill 也正好兜住 run 2 那种句柄泄漏不退出的形态,无需改动 guard 脚本。node -e时区断言留在 guard 之外:一次性打印不可能 stall,guard 只计时真正的 suite。--log是 guard 必填参数(guard 自己负责 tee);该 job 目前没有 completeness guard 消费这些日志,注释里已写明。pnpm --filter … test保持反斜杠续行,整体缩进一级放入 guard 之后;已本地验证 YAML 解析、bash -n续行语法、以及 guard 以相同参数干跑(exit 0)。Closes #4331
🤖 Generated with Claude Code
https://claude.ai/code/session_01HXjVcohpYTsZY7D5p91dJQ
Generated by Claude Code