Skip to content
This repository was archived by the owner on Dec 29, 2021. It is now read-only.
This repository was archived by the owner on Dec 29, 2021. It is now read-only.

main_binary's stderr may include extra text #79

Closed

Description

@epage
  • assert_cli version: 0.5.4
  • Rust version: 1.22
  • OS and version: Windows

By default, cargo test runs tests in parallel. When two tests invoke main_binary in parallel, cargo will block until the other instance of cargo is finished.

Unfortunately, it seems that cargo prints Blocking waiting for file lock on build directory to stderr, even with --quiet, or at least that is what I'm assuming is going wrong in cobalt-org/cobalt.rs#352

Activity

  1. epage commented on Jan 3, 2018

    @epage
    CollaboratorAuthor

    See #51 for a discussion on alternative ways of finding the test binary.

    One workaround for this issue is to serialize the tests. This gets annoying for random contributors because they won't know of the requirement.

    One workaround is requires more advanced stderr matching for clients to choose to detect and ignore this text.

  2. epage commented on Jan 3, 2018

    @epage
    CollaboratorAuthor

    Should cargo printing this despite --quiet be a bug?

  3. added a commit that references this issue on May 25, 2018
    d892f96
  4. epage commented on May 29, 2018

    @epage
    CollaboratorAuthor

    Addressed in assert_cmd
    https://github.com/assert-rs/assert_cmd
    assert_cli is going to morph into a wider-focused tool, including things like assert_fs. See #41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions