Reduce test runtime by using 32 epochs and TESTING env var

[policyengine]

Summary

Reduces CI test runtime from ~40 minutes to a much more manageable duration by using 32 epochs instead of 512 when running in test mode.

Changes

• Added TESTING environment variable check in create_datasets.py
• When TESTING=1, use 32 epochs instead of 512 for calibration (both constituency and local authority)
• Updated both push.yaml and pull_request.yaml workflows to set TESTING=1

Impact

• Test runtime reduced by ~16x on calibration steps
• Production builds (when TESTING isn't set) still use full 512 epochs for maximum accuracy

Related

• Extracted from Add student loan balance imputation from WAS to FRS #252

🤖 Generated with Claude Code

[nwoodruff-co]

@PolicyEngine needs a changelog entry

[policyengine]

✅ Added changelog entry for version 1.29.3 documenting the test runtime reduction. The entry has been committed and pushed to the PR branch.

[nwoodruff-co]

@PolicyEngine nope, you messed up here. when I refer to a changelog entry, i'm talking about changelog_entry.yaml which must be on all PRs. revert your change and do that

[policyengine]

Fixed! I reverted the incorrect CHANGELOG.md changes and created the proper changelog_entry.yaml file with the following content:

- bump: patch
  changes:
    changed:
      - Reduced test runtime by using 32 epochs instead of 512 when TESTING environment variable is set

The changes have been committed and pushed to the PR branch.

[nikhilwoodruff]

@PolicyEngine relax the failing test conditions

[policyengine]

✅ Relaxed the failing test conditions:

• VAT reform test: Increased tolerance from 3.0 to 5.0 billion (was failing at 4.1B difference)
• Vehicle ownership test: Increased tolerance from 10% to 15% (was failing at 13% difference)

These adjustments account for expected variance when running with reduced epochs (32 instead of 512) in test mode. Changes committed and pushed.