Skip to content

probe(ci): BLO-20869 — post-fix v2, force verify_serialized_server skipped, do not merge - #1009

Closed
allyblockcast[bot] wants to merge 2 commits into
masterfrom
probe/blo-20869-serialized-skip-postfix-v2
Closed

probe(ci): BLO-20869 — post-fix v2, force verify_serialized_server skipped, do not merge#1009
allyblockcast[bot] wants to merge 2 commits into
masterfrom
probe/blo-20869-serialized-skip-postfix-v2

Conversation

@allyblockcast

@allyblockcast allyblockcast Bot commented Aug 4, 2026

Copy link
Copy Markdown

Do not merge — throwaway probe, closing without merging once evidence is captured.

Rebased version of #958, stacked on the rebased fix (#1007) instead of the stale original. Same probe: verify_serialized_server forced to skipped via if: false, on top of the fix that folds its result into the verify aggregator.

Expected reading once checks settle: verify fails (the skipped lane is now asserted), so mergeStateStatus: BLOCKED — confirming the fix closes the gap.

Tracking: https://paperclip.blockcast.net/BLO/issues/BLO-20869
Fix under test: #1007

PlatformSREEngineer (Paperclip) and others added 2 commits August 4, 2026 09:07
…r (BLO-20869)

Fold verify_serialized_server's result into the existing if:always()
verify aggregator's lane_results check, alongside the other required
lanes. A cancelled, skipped, or never-scheduled serialized shard now
fails the one required check instead of being invisible to the merge
gate (mergeStateStatus reads BLOCKED instead of UNSTABLE/MERGEABLE).

Rebased onto current master: BLO-20867/#964 rewrote this job into a
bash lane_results map after the original fix branch was opened; this
carries the same change forward in that shape rather than reverting
#964's cancelled-vs-failed distinction.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
…ipped, do not merge

On top of the rebased fix (fix/blo-20869-require-serialized-server-v2):
a skipped serialized shard should now fail the required verify check
and the PR should read BLOCKED. Throwaway -- closing without merging
once the reading is captured.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@allyblockcast

allyblockcast Bot commented Aug 4, 2026

Copy link
Copy Markdown
Author

🔗 Paperclip issue: BLO-20869

1 similar comment
@allyblockcast

allyblockcast Bot commented Aug 4, 2026

Copy link
Copy Markdown
Author

🔗 Paperclip issue: BLO-20869

@allyblockcast

allyblockcast Bot commented Aug 4, 2026

Copy link
Copy Markdown
Author

Hey @allyblockcast[bot]! Before this PR can be reviewed, a few things need attention:

Missing or incomplete:

  • Missing section: ## Thinking Path
  • Missing section: ## What Changed
  • Missing section: ## Verification
  • Missing section: ## Risks
  • Missing section: ## Model Used
  • Add the dedup-search checkbox to your PR description and check it once you have searched the GitHub PR list for similar PRs. See the PR template at .github/PULL_REQUEST_TEMPLATE.md and CONTRIBUTING.md → "Before You Start: Search First".

Once updated, push a new commit and these checks will re-run automatically.

— commitperclip

@allyblockcast

allyblockcast Bot commented Aug 4, 2026

Copy link
Copy Markdown
Author

Ally — Consolidated PR Review

Lenses: pr-review-toolkit (code, tests, comments, errors, types) + gstack/review + native-codex.
Reviewed head: 22f63a0

Looks good for its stated throwaway-probe purpose. The forced skip reaches the real required-check aggregator, and the exact-head policy job passed with the added lane-outcome tests.

Suggestions (1)

  • [tests] scripts/__tests__/pr-verify-lane-outcome.test.mjs:57 — Consider adding structural assertions that verify.needs contains verify_serialized_server and that needs.verify_serialized_server.result feeds VERIFY_SERIALIZED_SERVER_RESULT. The live probe covers the wiring now, while assertions would make future regressions more local and explicit.

Strengths

  • The probe is clearly marked as non-shipping and deliberately forces the precise skipped state under test.
  • The aggregator uses always() and classifies skipped, cancelled, and failed outcomes separately.
  • The new tests exercise all three non-success outcomes for the serialized lane.

Recommended Action

  1. Capture the expected failing verify result, then close this probe without merging as described in the PR.
  2. Because this PR is authored by app/allyblockcast, the App cannot review its own PR. The exact head must be reopened under an independent author before an App approval is possible; the shared merge-token user is not a substitute for the App gate review.

@kkroo

kkroo commented Aug 4, 2026

Copy link
Copy Markdown

Closing the throwaway BLO-20869 post-fix probe per the PR body. Evidence was captured by the settled blocked check state; the real fix remains #1007.

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