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

Moduletest: Test only the executable for the right build #35

Closed
anordal opened this issue Sep 20, 2020 · 0 comments
Closed

Moduletest: Test only the executable for the right build #35

anordal opened this issue Sep 20, 2020 · 0 comments

Comments

@anordal
Copy link
Owner

anordal commented Sep 20, 2020

The module test (aka. integration test) doesn't know if cargo test is invoked with --release or not.

That is the fundamental problem. Furthermore, it doesn't really want to concern itself with where the various debug and release executables are located.

Currently, it searches for executables named "shellharden" and just tests every one of them. Care is taken to search CARGO_TARGET_DIR if set.

Why this is wrong: When you think you are testing the debug build, you are implicitly also testing a stale release build if it exists, and vice versa.

Problem:
rust-lang/cargo#3670

Solution:
rust-lang/cargo#7697

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant