Skip to content

ci: clarify Go replay backend reporting - #524

Merged
vuanhphung merged 1 commit into
mainfrom
chore/go-replay-dispatch-messages
Oct 30, 2026
Merged

vuanhphung merged 1 commit into
mainfrom
chore/go-replay-dispatch-messages

Conversation

@vuanhphung

Copy link
Copy Markdown
Collaborator

Replay dispatches now run both Thrift and SEA in driver-test, but the Go workflow still describes Thrift-only coverage. Update its comments, dispatch logs, and PR notification to report both replay backends; live previews report the selected backend.

Validated with actionlint, YAML and JavaScript syntax checks, and git diff --check.

Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
@vuanhphung
vuanhphung marked this pull request as ready for review October 30, 2026 19:21

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: 1 Nit

Looks good. This PR only updates comments, log messages and the PR comment text, and the backends ternary is correct for each label → mode mapping. One nit: the payload still sends go_mode: 'thrift' on replay while the logs report thrift+sea.

Other findings

  • ⚪ Nit — Replay dispatches still send go_mode: 'thrift' (merge-queue L262 and the * branch in the label step), while the logs and PR comment now say thrift+sea. That's only accurate as long as driver-test ignores go_mode in replay mode. Consider sending a neutral value such as go_mode: 'all', or adding a comment that go_mode is ignored for replay, so the payload and the reported backends don't contradict each other.

@vuanhphung
vuanhphung enabled auto-merge October 30, 2026 19:27
@vuanhphung
vuanhphung added this pull request to the merge queue Oct 30, 2026
Merged via the queue into main with commit a3c06de Oct 30, 2026
12 of 13 checks passed
@vuanhphung
vuanhphung deleted the chore/go-replay-dispatch-messages branch October 30, 2026 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant