Precompile repeated imports in disposable test copies

Compile repeated imports once per test shard when every test subprocess runs with bytecode writes off.

Prompt

Evaluate and apply this CI technique to my repository: Precompile repeated imports in disposable test copies.

Compile repeated imports once per test shard when every test subprocess runs with bytecode writes off.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/precompile-test-imports.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How OpenAI used this technique

Read what OpenAI changed and follow the original sources.

Precompile repeated imports in disposable test copies

Codex Security runs compileall with checked hashes on each shard's disposable copy of the package. Release artifacts keep the original archive, and the isolated subprocesses keep their no-write flags.

Paired local Linux run of the 43 scan-resume cases: 451.7s to 381.7s, plus 1.1s of preparation Source

Use it when: Tests launch many isolated interpreters with bytecode writes disabled.
Before applying it: Generated bytecode stays out of release artifacts. Hash-based invalidation, interpreter compatibility and the real no-write tests remain necessary.

How OpenAI used this technique

Precompile repeated imports in disposable test copies

Company Playbooks