lathe_field_sim: multi_pass_contour_simulates_with_meridian_parity takes about 107 s in debug

Open Beginner friendly
#1,855 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
testing

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

area:sim area:turning effort:low P7 source:agent

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NeoTech/Camcraft

All issues in NeoTech/Camcraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.