You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The affected PR verification gate runs turbo run build typecheck test in one invocation. Although Turbo declares test and typecheck as depending on each package build, unrelated package builds can still mutate shared dependency outputs while consumers are testing or typechecking. The required validate check is therefore failing nondeterministically on packages unrelated to the PR diff.
PR fix: reject lossy metering usage values #1630 head bea6c31537bd414a3bb91f74b32ed132820d8c57 failed the same combined gate first in @croco/cli#test; its later standalone test gate passed, and the CLI suite passes locally.
Rerunning the unchanged PR head/base failed the combined gate in both @croco/cli#test and @croco/rpc-codegen#typecheck; standalone rpc-codegen typecheck passes locally.
A local reproduction of the exact combined command failed only @croco/rpc-codegen#typecheck (345/346 tasks), followed by a passing standalone rpc-codegen typecheck.
The affected verification profile should preserve the same build, typecheck, and test coverage while preventing build output mutation from racing dependent checks. For example, complete affected builds before running affected typechecks/tests, and retain deterministic failure diagnostics. Add a verification-manifest contract test for the ordering.
Acceptance criteria
Affected build completes before dependent affected typecheck/test execution.
The current affected package filter semantics remain intact.
Verification manifest tests prove the ordering/commands.
Repeated affected verification runs do not produce moving CLI/rpc-codegen failures on an unchanged tree.
Blocks #1630 and likely other PRs until the required validate gate is stable.
Problem
The affected PR verification gate runs
turbo run build typecheck testin one invocation. Although Turbo declarestestandtypecheckas depending on each package build, unrelated package builds can still mutate shared dependency outputs while consumers are testing or typechecking. The requiredvalidatecheck is therefore failing nondeterministically on packages unrelated to the PR diff.Evidence
88c6ce10feb24a70183e3d3c4bb4c0edfcf705e6failed CI run https://github.com/croco-dev/framework/actions/runs/30576218296 in@croco/cli#test; the later standalone summarized test gate passed in the same job.bea6c31537bd414a3bb91f74b32ed132820d8c57failed the same combined gate first in@croco/cli#test; its later standalone test gate passed, and the CLI suite passes locally.@croco/cli#testand@croco/rpc-codegen#typecheck; standalone rpc-codegen typecheck passes locally.@croco/rpc-codegen#typecheck(345/346 tasks), followed by a passing standalone rpc-codegen typecheck.Expected outcome
The affected verification profile should preserve the same build, typecheck, and test coverage while preventing build output mutation from racing dependent checks. For example, complete affected builds before running affected typechecks/tests, and retain deterministic failure diagnostics. Add a verification-manifest contract test for the ordering.
Acceptance criteria
Blocks #1630 and likely other PRs until the required
validategate is stable.