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

"make check" does not always catch a missing executable #39

Open
teuben opened this issue Nov 21, 2020 · 5 comments
Open

"make check" does not always catch a missing executable #39

teuben opened this issue Nov 21, 2020 · 5 comments

Comments

@teuben
Copy link
Owner

teuben commented Nov 21, 2020

a missing executable doesn't trigger a FAIL message in "make check"

@teuben
Copy link
Owner Author

teuben commented Sep 2, 2021

not clear if this is still an issue: removing an BIN= (or even a NEED=) binary from a Testfile
directory correctly shows FAIL now.

@teuben
Copy link
Owner Author

teuben commented Sep 2, 2021

Found a case: remove ccdrow and perhaps being in a pipe, it does not correctly report a FAIL

@teuben
Copy link
Owner Author

teuben commented Oct 8, 2021

The solution should be that for every target in the BIN= in a Testfile, there needs to be a direct test in that target without being in that pipe, viz.

foobar:
$(EXEC) foobar ... ; nemo.coverage foobar.c

though additional tests are sstill useful to test other aspects of the program. @Vmbundu

@Vmbundu
Copy link

Vmbundu commented Oct 8, 2021 via email

@teuben
Copy link
Owner Author

teuben commented Jan 4, 2025

See also #14

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

No branches or pull requests

2 participants