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

Problem: ./mlm_selftest can't find .cfg files in mlm_client selftests and fails #335

Closed
wants to merge 1 commit into from

Conversation

BHare1985
Copy link

Solution: Add configure_file calls to CMakeLists


WARNING: This modifies a zproject generated file.

This is meant as a quick-fix for those stump as to why mlm_client selftest fails with the following when executing mlm_selftest

 * mlm_client:
W: 24-03-27 13:53:44 cannot load config file 'src/mlm_client.cfg'
I: 24-03-27 13:53:44 My address is 'client_robust'
mlm_selftest: /home/brian/malamute/src/mlm_client.c:897: mlm_client_test: Assertion `rc == 0' failed.

When running cmake from clion IDE, the default behavior is that mlm_selftest is it's own test project you can execute, but when doing so the authorization fails (relating to not finding .cfg). I have yet to dive into the depths of how this could be done with zproject properly, and I tried implementing the suggestion of moving them to /src/selftests_ro ( #272 ) but that was honestly a lot of changes and they wouldn't of been valid anyways since they were modifying zproject generated files.

Not reading in mlm_client.cfg failed gracefully with a warning, but sending PLAINto the auth actor with non-existant passwords.cfg is out the scope of malamute (different repo) but would be nice if it also warned.

Solution: Add `configure_file` calls to CMakeLists
@BHare1985
Copy link
Author

Clarification: zauth does warn about not loading the cfg file but only when VERBOSE is true, which is different than malamute.

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