Repository navigation
Commit 9b0600b
committed
bench: record type_name_surrogate_reject's dynasm and cranelift jit-stats at the value CI measures
The dynasm and cranelift baselines carried `loops_aborted=0`,
`guard_failures=18923`, `fbw_blackhole_adopted_single_frame=0`, snapshotted
from a build on this machine. All three `pyre/check.py` legs of the PR run
(ubuntu-24.04, windows-latest, macos-latest) report the same other vector on
both backends instead: `loops_aborted=1`, `guard_failures=17799`,
`fbw_blackhole_adopted_single_frame=1`, with `loops_compiled=2` and
`bridges_compiled=0` unchanged. None of the three legs flagged the row
`UNSTABLE`, so the re-run each performs read the same counters again.
The `.wasm` baseline already carries `loops_aborted=1` and
`fbw_blackhole_adopted_single_frame=1`, and its sandbox job passed.
`MAJIT_LOG=1` on this machine's build counts 18922
`handle_async_forcing] forced` lines against `guard_failures=18923`, and no
`abort trace at key=` line.
Assisted-by: Claude1 parent 8a15e09 commit 9b0600b
2 files changed
Lines changed: 6 additions & 6 deletions
File tree
- pyre/bench/synth
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
6 | | - | |
| 6 | + | |
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
11 | | - | |
| 11 | + | |
12 | 12 | | |
13 | | - | |
| 13 | + | |
14 | 14 | | |
15 | 15 | | |
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
6 | | - | |
| 6 | + | |
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
11 | | - | |
| 11 | + | |
12 | 12 | | |
13 | | - | |
| 13 | + | |
14 | 14 | | |
15 | 15 | | |
0 commit comments