Skip to content

Add a warning if default-members are configured and no package selection arguments are passed in #695

Open
@milesj

Description

@milesj

I've noticed something very weird recently. When running with cargo nextest run, the entire suite would pass with no issue:

Summary [  85.492s] 292 tests run: 292 passed, 0 skipped

While debugging individual tests, I started noticing tests that were "passing" started failing, but after looking into them, they were definitely broken and had to be fixed. I have no idea why nextest was passing. Were this just being ignored/filtered? Was nextest failing to capture/run them? No idea.

When running with cargo test --workspace, there are many failing tests. I'm unable to run the entire suite to determine an exact number without fixing them all (which I'm in the process of doing anyways). You can verify all of this in my branch here: https://github.com/moonrepo/moon/tree/develop-0.21

Things I've noticed that are failing:

  • Tests that use #[serial] from serial_test.
  • Tests using #[should_panic].

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions