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

added environment variable TEST_CPPCHECK_INJECT_BUILDDIR to inject --cppcheck-build-dir into the cppcheck invocation of Python tests #6876

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

firewave
Copy link
Collaborator

@firewave firewave commented Oct 7, 2024

No description provided.

@firewave

This comment was marked as resolved.

@firewave firewave changed the title added environment variable TEST_CPPCHECK_INJECT_BUILDDIR to inject … added environment variable TEST_CPPCHECK_INJECT_BUILDDIR to inject --cppcheck-build-dir into the cppcheck invocation of Python tests Oct 7, 2024
@firewave
Copy link
Collaborator Author

firewave commented Oct 7, 2024

So far I still stand by my previous comment that the build dir should not be used in production ... if all tests pass with the option injected I will most likely change my opinion.

@firewave

This comment was marked as resolved.

@firewave firewave force-pushed the inject-builddir branch 3 times, most recently from edb18d6 to b326a34 Compare October 21, 2024 12:31
@firewave
Copy link
Collaborator Author

So far I still stand by my previous comment that the build dir should not be used in production ... if all tests pass with the option injected I will most likely change my opinion.

This looks better than expected and I take back my previous opinion. There are still documented issues but those don't look too bad.

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

Successfully merging this pull request may close these issues.

1 participant