Skip to content
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.

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

Compilation error in cargo-maelstrom leaves weird output #445

Open
nfachan opened this issue Jan 14, 2025 · 0 comments
Open

Compilation error in cargo-maelstrom leaves weird output #445

nfachan opened this issue Jan 14, 2025 · 0 comments
Labels
bug Something isn't working cargo-maelstrom test-runners Issues that affect all test runners (cargo-maelstrom, maelstrom-pytest, maelstrom-to-test, etc.).
Milestone

Comments

@nfachan
Copy link
Collaborator

nfachan commented Jan 14, 2025

Specific Maelstrom Program?
cargo-maelstrom and likely maelstrom-go-test

Bug Description
There is a missing newline and carriage return when a compilation issue arises. Also, the summary seems to be output for some reason.

How to Reproduce
Introduce a compilation error.

Expected Behavior
Better, cleaner output.

Additional Context
For example:

neal-desktop:~/maelstrom[101]% cargo maelstrom --include 'package.eq(maelstrom-test-runner)'
Jan 14 22:57:50.787 INFO [client-process] cache initialized, byte_used_target: 1000.0 MB, bytes_used: 31.7 MB, entries: 458
                                                       Test Summary
Successful Tests                                                                                                 0
Failed Tests                                                                                                     0
Tests Not Run                                                                                                    ~192
                                                    Collection Outputerror: recursion limit reached while expanding `$crate::container_spec!`
   --> crates/maelstrom-test-runner/src/metadata/directive.rs:967:61
    |
967 |                       container: DirectiveContainer::Override(container_spec! {
    |  _____________________________________________________________^
968 | |                         user: 101,
969 | |                         grous: 202,
970 | |                     }),
    | |_____________________^
    |
    = help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`maelstrom_test_runner`)
    = note: this error originates in the macro `$crate::container_spec` which comes from the expansion of the macro `container_spec` (in Nightly builds, run with -Z macro-backtrace for more info)

error: could not compile `maelstrom-test-runner` (lib test) due to 1 previous error

neal-desktop:~/maelstrom[101]%
@nfachan nfachan added bug Something isn't working cargo-maelstrom test-runners Issues that affect all test runners (cargo-maelstrom, maelstrom-pytest, maelstrom-to-test, etc.). labels Jan 14, 2025
@nfachan nfachan added this to the 0.13.0 milestone Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cargo-maelstrom test-runners Issues that affect all test runners (cargo-maelstrom, maelstrom-pytest, maelstrom-to-test, etc.).
Projects
None yet
Development

No branches or pull requests

1 participant