Skip to content

cargo maelstrom --stop-after=1 doesn't stop immediately while artifacts are still being built #414

@nfachan

Description

@nfachan

Specific Maelstrom Program?
cargo maelstrom, though probably also an issue for maelstrom-go-test.

Bug Description
After a test fails, with --stop-after=1 passed, the test runner doesn't immediately exit.

How to Reproduce
One way to reproduce is to run cargo maelstrom. Then, edit one test to make it fail. Re-run cargo maelstrom (with --stop-after=1 to make it fast). Then, edit a test in a different package and re-run cargo maelstrom --stop-after=1. The test will fail immediately, but the test runner will continue on until the newly-modified test is rebuilt.

Expected Behavior
It should exit immediately after the failure.

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions