Split CI cargo run and test into build then execute (#8705) · RustPython/RustPython@39b7030 · GitHub
Skip to content

Commit 39b7030

Browse files
authored
Split CI cargo run and test into build then execute (#8705)
* Run gc_collect ten times per benchmark iteration Assisted-by: Grok:4.6 * Reuse the prebuilt rustpython for CI whats_left whats_left was invoking cargo build --release without threading, so the snippets job rebuilt the interpreter after the earlier release build. Assisted-by: Grok:4.6 * Split CI cargo run and test into build then execute Assisted-by: Grok:4.6 * Compile doctests in the CI build step cargo test --no-run skips doctests, so rustdoc compilation was still happening in the run step. Assisted-by: Grok:4.6 * Drop cron-ci.yaml from this PR A pull_request path filter matches the whole PR, so every push was starting the periodic benchmark and coverage jobs. Assisted-by: Grok:4.6 * Run doctests in their own CI step cargo test --doc --no-run is rejected, so doctests cannot be compiled without also executing them. Assisted-by: Grok:4.6 * Do not run benchmark targets in rust tests --all-targets includes Criterion benches, which cargo test does not run by default. Assisted-by: Grok:4.6
1 parent b6fc810 commit 39b7030

3 files changed

Lines changed: 84 additions & 27 deletions

File tree

.github/workflows/ci.yaml

Lines changed: 52 additions & 12 deletions

benches/benchmarks/gc_collect.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,4 +52,4 @@ def benchamark_collection(loops, cycles, links):
5252

5353
assert collected is None or collected >= cycles * (links + 1)
5454

55-
benchamark_collection(1, CYCLES, LINKS)
55+
benchamark_collection(10, CYCLES, LINKS)

scripts/whats_left.py

Lines changed: 31 additions & 14 deletions

0 commit comments

Comments
 (0)