Skip to content

Build pecos-stab-tn at opt-level 2 in dev and test profiles like the other simulation crates #709

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ciaranra merged 2 commits into from
Sep 8, 2026
+5 −0
Merged

Build pecos-stab-tn at opt-level 2 in dev and test profiles like the other simulation crates #709

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
50adb15
Build pecos-stab-tn at opt-level 2 in dev and test profiles like the …
ciaranra Sep 4, 2026
588537d
Merge remote-tracking branch 'origin/dev' into wt-ci-stab-tn-opt-level
ciaranra Sep 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -298,6 +298,9 @@ clone_on_copy = "allow" # `cxx::bridge` derives `Clone` for its generated FFI st
# statistical validation tests (e.g. the surface-code LER equivalence
# gate) need tens of thousands of simulated shots and are unusably slow
# unoptimized (>10 min vs ~2 min). Debug assertions remain enabled.
# pecos-stab-tn is on the list for the same reason: its unit tests take
# 159 s unoptimized and 6 s at opt-level 2 (measured 2026-09-04), and they
# were the second-largest share of the PR gate's Rust test time.
[profile.dev.package.pecos-core]
opt-level = 2
[profile.dev.package.pecos-random]
Expand Down Expand Up @@ -325,6 +328,8 @@ opt-level = 2
opt-level = 2
[profile.dev.package.relay-bp]
opt-level = 2
[profile.dev.package.pecos-stab-tn]
opt-level = 2

# batsat's solver core is tested and shipped by upstream with release arithmetic;
# under this workspace's debug profile its internal activity/restart arithmetic
Expand Down
Loading