test(ci): verify executable changes and boundary tests on live CI - #2207
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Live execution evidence (run 34965621059): Build passed. All five InvalidTemperature_Throws cases and all three ValidTemperature_ProducesNormalizedProbabilities cases passed in Integration A-B at 12:16:59 UTC. The current certified map selected 4/116, not the initial expected 2: C-Core, D, and N-O are now mandatory shards. Integration A-B and D passed; C-Core and N-O failed. Regression analysis classified exactly two persistent baseline failures, zero new failures, and zero unresolved touched-surface risks; Validation Gate and expensive certificate publication passed. This is not an all-green shard claim. CodeQL and Sonar remain in progress. Negative fixture #2208 keeps all assertions and changes <= to < to deliberately fail the zero-temperature case. Changed-base fixture #2209 merged only into an isolated branch; run 34972082280 explicitly deferred with a non-passing gate and no duplicate matrix while source validation remains in progress. Changed-base resumption and negative rejection are still unproven. |
|
All-green runtime acceptance rerun: head 20129ba, isolated baseline 27bea74 (master including #2205 plus the locally verified #2213 runtime/build fixes). Baseline setup deliberately skipped CI; it is not master validation evidence. PR diff remains exactly the GumbelSoftmax executable guard and its tests, with no PR-local workflow override. Run 35002245392 must build, select the affected shards, execute the positive assertions and both previously failing runtime tests, then publish Validation evidence. A queued/skipped run is not acceptance. Changed-base all-green reuse/import follows only after that evidence is available. |
|
Live selector evidence for head 20129ba: job 104496257488 completed successfully and emitted selected 4 of 116, escalated=false. Matrix is Integration A-B (affected code/tests), plus mandatory Integration C - Core, D, N-O. Build job 104498826702 is queued, so this proves scheduling only; executed tests and certificate publication are not yet claimed. https://github.com/ooples/AiDotNet/actions/runs/35002245392/job/104496257488 |
|
Deployment failed for project aidotnet_website with the following error: Learn More: https://vercel.com/franklins-projects-02a0b5a0?upgradeToPro=build-rate-limit |
|
Deployment failed for project aidotnet-playground-api with the following error: Learn More: https://vercel.com/franklins-projects-02a0b5a0?upgradeToPro=build-rate-limit |
1 participant
ISOLATED ACCEPTANCE FIXTURE: never merge this proof branch into master. Unlike the previous comment-only canary, this changes executable constructor behavior to reject invalid temperatures and adds five rejection cases plus three valid-output cases to an existing mapped integration class. CI must build the changed source and tests and execute those assertions. No workflow changes, map overrides, skipped correctness assertions, or synthetic certificates. Expected affected shard selection is Integration A-B plus mandatory Integration D. Live build/test results pending; local checks are diff inspection and git diff --check only. After genuine validation, follow-up isolated cases will introduce a deliberate regression and a changed-base runtime delta to test rejection of stale evidence and delta-specific reruns. Sonar is not being counted as correctness proof.