lathe_field_sim: multi_pass_contour_simulates_with_meridian_parity takes about 107 s in debug
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start in the lathe_field_sim test binary and find multi_pass_contour_simulates_with_meridian_parity; read the fixture setup it builds before running it with cargo test --test lathe_field_sim multi_pass_contour_simulates_with_meridian_parity in debug to confirm the ~107 s timing. Then either shrink the fixture so the same asserts still hold, or add #[ignore] naming the heavy lane and list it in the release tier config. Done when debug runtime is under 60 s or the ignore plus lane listing is in place, with asserts unchanged.
Written by the indexing model from the issue text.
Description
What is wrong: the test multi_pass_contour_simulates_with_meridian_parity in the lathe_field_sim test binary takes about 107 s in debug. The rule is to move a test over about 60 s to the heavy lane or to use a smaller fixture.
Evidence: PR #1838 comment on #1715. The test is one field-engine job, so a split gives no gain.
Part of #1715.
Done means: the test uses a smaller fixture and runs in under 60 s in debug. Or it is #[ignore]d with a reason that names the heavy lane, and the release tier lists it. Its asserts stay the same.
- Dominant language
- Rust
- Stars
- 8
- Forks
- 11
- Avg merge
- 6h 45m
- Merged PRs (30d)
- 905
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NeoTech/Camcraft
-
area:ui bug effort:low P2 source:agent
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
area:ui effort:low enhancement P7 source:agent
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NeoTech/Camcraft#2039 · 3 comments ·
Maintainers usually reply within 1 day
-
area:turning area:ui effort:low P7 source:agent
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
area:build effort:low P7 source:agent
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
post-merge.yml: the report job is skipped when the gate fails, so a red main opens no issuePossibly taken @tbrasselle claimed this today. Openarea:build bug claimed effort:low P5 source:agent
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
NeoTech/Camcraft#1611 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in NeoTech/Camcraft
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yantrikos/yantrik-os#1272 ·
Maintainers usually reply within 1 day
-
crate: spate-kafka priority: low tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·