Skip to content

[ci] Guard consolidated build and test jobs - #3561

Open
joshlf wants to merge 1 commit into
G386fde8c9c2d7c96a9f67f5f5a0f5a64from
G4ad937d415e180e0db2a85c15fbe30d3
Open

[ci] Guard consolidated build and test jobs#3561
joshlf wants to merge 1 commit into
G386fde8c9c2d7c96a9f67f5f5a0f5a64from
G4ad937d415e180e0db2a85c15fbe30d3

Conversation

@joshlf

@joshlf joshlf commented Aug 19, 2026

Copy link
Copy Markdown
Member

Consolidate an ordinary native cell only when its audited feature
selection enables an integration target. Otherwise retain a separate
build, since unit tests do not prove the normal library artifact.
Always retain the build for proc macros: Cargo 1.56 does not emit their
dev artifact from cargo test, and zerocopy-derive's dev-only
syn/visit feature otherwise masks its production syn/full graph.
An independent current-state audit checks the exact required builds
without rewriting immutable historical evidence.

Reject a root [profile.test], any CI CARGO_PROFILE_TEST_* override,
and a non-unwind dev panic strategy. Keep other dev settings supported,
while rejecting Cargo configuration and profile selectors that would
change consolidated jobs. Run a centralized cargo tree smoke test in
check_tools as a review reminder for dev-dependency feature
unification, while keeping its documented approximation explicit.

The original 44-cell consolidation reduced non-Anneal PR wall time
from 5:32 to 4:04 against its then-parent. Across two comparable
baselines, the average reduction was 73 seconds (23%), while total
runner time across the 60-job matrix fell by 30:03 (17.3%). This
change preserves consolidation in 38 of 44 native cells; the measured
figures are therefore an upper bound until the six short proc-macro
builds are remeasured.

Authored by an agent, posting via joshlf's account


Latest Update: v7 — Compare vs v6

📚 Full Patch History

Links show the diff between the row version and the column version.

Version v6 v5 v4 v3 v2 v1 Base
v7 vs v6 vs v5 vs v4 vs v3 vs v2 vs v1 vs Base
v6 vs v5 vs v4 vs v3 vs v2 vs v1 vs Base
v5 vs v4 vs v3 vs v2 vs v1 vs Base
v4 vs v3 vs v2 vs v1 vs Base
v3 vs v2 vs v1 vs Base
v2 vs v1 vs Base
v1 vs Base
⬇️ Download this PR

Branch

git fetch origin refs/heads/G4ad937d415e180e0db2a85c15fbe30d3 && git checkout -b pr-G4ad937d415e180e0db2a85c15fbe30d3 FETCH_HEAD

Checkout

git fetch origin refs/heads/G4ad937d415e180e0db2a85c15fbe30d3 && git checkout FETCH_HEAD

Cherry Pick

git fetch origin refs/heads/G4ad937d415e180e0db2a85c15fbe30d3 && git cherry-pick FETCH_HEAD

Pull

git pull origin refs/heads/G4ad937d415e180e0db2a85c15fbe30d3

Stacked PRs enabled by GHerrit.

@codecov-commenter

codecov-commenter commented Aug 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.85%. Comparing base (5b71dd8) to head (38b706d).

Additional details and impacted files
@@                        Coverage Diff                         @@
##           G386fde8c9c2d7c96a9f67f5f5a0f5a64    #3561   +/-   ##
==================================================================
  Coverage                              91.85%   91.85%           
==================================================================
  Files                                     20       20           
  Lines                                   6093     6093           
==================================================================
  Hits                                    5597     5597           
  Misses                                   496      496           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

joshlf commented Aug 19, 2026

Copy link
Copy Markdown
Member Author

Authored by Codex, posting via joshlf's account

@codex review

Please review the current exact head after the stack reorder and recovery.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 4be51ba706

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@joshlf
joshlf force-pushed the G386fde8c9c2d7c96a9f67f5f5a0f5a64 branch from f7e334e to 3d2f255 Compare August 19, 2026 13:54
@joshlf
joshlf force-pushed the G4ad937d415e180e0db2a85c15fbe30d3 branch from 4be51ba to 0caf293 Compare August 19, 2026 13:54
@joshlf

joshlf commented Aug 19, 2026

Copy link
Copy Markdown
Member Author

Authored by Codex, posting via joshlf's account

@codex review

Please review the current exact head after addressing the prior feedback.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 0caf293236

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@joshlf

joshlf commented Aug 27, 2026

Copy link
Copy Markdown
Member Author

Authored by an agent, posting via joshlf's account

@jswrenn, this reconstructs #3506 at the bottom of the current stack. The commit message now describes the affected jobs directly, explains the Cargo profile assumption and safeguards in plain language, and retains the measured latency and runner-time results.

Would you please re-review current head 74eb8bf?

@joshlf

joshlf commented Aug 27, 2026

Copy link
Copy Markdown
Member Author

Authored by an agent, posting via joshlf's account

@codex review

Please review the current head, 74eb8bf9f9cb20b008aa6ce9fa097f19506dd374.

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 74eb8bf9f9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread tools/zc/src/metadata.rs
@joshlf
joshlf force-pushed the G4ad937d415e180e0db2a85c15fbe30d3 branch from 74eb8bf to e990345 Compare August 27, 2026 16:42
@joshlf

joshlf commented Aug 27, 2026

Copy link
Copy Markdown
Member Author

Authored by an agent, posting via joshlf's account

@codex review

Please review the current head, e990345acf92a811b038ff6d1d363a9050dd6762.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Bravo.

Reviewed commit: e990345acf

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Consolidate an ordinary native cell only when its audited feature
selection enables an integration target. Otherwise retain a separate
build, since unit tests do not prove the normal library artifact.
Always retain the build for proc macros: Cargo 1.56 does not emit their
dev artifact from `cargo test`, and `zerocopy-derive`'s dev-only
`syn/visit` feature otherwise masks its production `syn/full` graph.
An independent current-state audit checks the exact required builds
without rewriting immutable historical evidence.

Reject a root `[profile.test]`, any CI `CARGO_PROFILE_TEST_*` override,
and a non-unwind dev panic strategy. Keep other dev settings supported,
while rejecting Cargo configuration and profile selectors that would
change consolidated jobs. Run a centralized `cargo tree` smoke test in
`check_tools` as a review reminder for dev-dependency feature
unification, while keeping its documented approximation explicit.

The original 44-cell consolidation reduced non-Anneal PR wall time
from 5:32 to 4:04 against its then-parent. Across two comparable
baselines, the average reduction was 73 seconds (23%), while total
runner time across the 60-job matrix fell by 30:03 (17.3%). This
change preserves consolidation in 38 of 44 native cells; the measured
figures are therefore an upper bound until the six short proc-macro
builds are remeasured.

*Authored by an agent, posting via joshlf's account*

gherrit-pr-id: G4ad937d415e180e0db2a85c15fbe30d3
@joshlf
joshlf force-pushed the G4ad937d415e180e0db2a85c15fbe30d3 branch from e990345 to 38b706d Compare August 27, 2026 16:59
@joshlf

joshlf commented Aug 27, 2026

Copy link
Copy Markdown
Member Author

Authored by an agent, posting via joshlf's account

@codex review

Please review the current head, 38b706dd35649c93079f2bfeb91a586012111ab2.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Chef's kiss.

Reviewed commit: 38b706dd35

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

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.

2 participants