-
Notifications
You must be signed in to change notification settings - Fork 51
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
Comments
not clear if this is still an issue: removing an BIN= (or even a NEED=) binary from a Testfile |
Found a case: remove ccdrow and perhaps being in a pipe, it does not correctly report a FAIL |
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: though additional tests are sstill useful to test other aspects of the program. @Vmbundu |
Understood
…On Fri, Oct 8, 2021 at 9:25 AM Peter Teuben ***@***.***> wrote:
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 <https://github.com/Vmbundu>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALE7F2GWYSNH2VHPTZ2M5LLUF3WN7ANCNFSM4T5Z3O3A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
See also #14 |
a missing executable doesn't trigger a FAIL message in "make check"
The text was updated successfully, but these errors were encountered: