Repository navigation
refactor(bench): enforce GDC diagnostic measurement boundaries (#959) - #1493
Conversation
Centralize fail-closed checks that live GDC evidence must keep certification:false, reject BenchExec authority on in-process runners, and never treat resource timings as performance-gate inputs. Inventory now includes gdc-snb-bi. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: CurateLabs/graphforge/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. 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 |
Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
gdc_measurement_policy.pywith fail-closed checks that live GDC evidence keepscertification: false, rejects misattributed BenchExec authority on in-process runners, and never treatsresources.correctness_authorityas a performance-gate input.gdc-snb-biin the benchmark measurement inventory.Test plan
PYTHONPATH=harness uv run --locked python -m unittest tests.test_gdc_measurement_policyPYTHONPATH=harness uv run --locked python -m unittest tests.test_gdc_snb_bi -k livepython3 scripts/ci/benchmark-measurement-policy.pyPart of #959 (lifecycle/GDC measurement-boundary slice).