Repository navigation
Update the subsample policy-binding test for policyengine-core 3.33.1 - #10069
Merged
Merged
Conversation
Contributor
Author
|
US + core hub merge audit, us#10069 at
|
This was referenced Oct 10, 2026
Merged
Merged
Contributor
Author
|
Local two-core results for this change, as promised in the description (run by the build job at
So the updated test holds under both the recorded-input rebuild (3.33.1) and the earlier behaviour that exported calculated values. The full |
This was referenced Oct 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The SPM policy-binding property test assumed calculated reform values became inputs during every subsample rebuild. Core #573, released in policyengine-core 3.33.1, now rebuilds from surviving recorded inputs instead, so indexing an absent calculated
reform_only_incomeholder raisedKeyErrorand failed the Microsimulation job's Run SPM Python tests step.Failing CI evidence: run 38074706313, job 114279224752 and run 38074181952, job 114277668349. Upstream contract: core#573.
After each subsample, the test recalculates both the reform-only and redefined variables, then verifies their holders have known periods and non-eternal storage. It retains every existing ownership assertion and the explicit repeated-subsample example, rechecks the newly populated reform holders, and explicitly excludes the reform-only holder from the baseline. Populations, holders, and recorded input names must remain bound to each arm's own policy under either core behavior.
Read-only audit of
system.pyandspm.pyfound no production dependency on calculated caches surviving as inputs. Holder rebinding and baseline cleanup operate on existing holders, and input transformations use recordedset_inputcalls. The obsolete export comments were confined to this test and are corrected here. No production code or partner tests changed.Validation:
test_spm_system.py; the subsequent microsimulation tests reported 130 passed, 4 skipped. The merge gate still requires the latestPull requestrun at exact head9b06402dd1291b7dd199a979a5adc1b83c0fd965to conclude success before the hub merges.9b06402dd1. It traced the test against the core 3.33.1 source and checked both holder expectations by hand; it ran no tests.test_spm_system.pyfile on core 3.33.1 remains pending; its counts will be added to this body after completion.make format(Ruff formatting) andgit diff --checkpass.axiom: n/a: test-only change, no policy change
Hub microsimulation impact: none (test-only). No local microsimulation was run. The diff at
9b06402dd1changes two files,policyengine_us/tests/core/test_spm_system.pyandchangelog.d/hub-fix-spm-subsample-test-core-3331.fixed.md. No variable, parameter, reform or data file changes.Opened by the US + core hub: this failure blocks CI on every open PE-US pull request.
🤖 Generated with Claude Code