-
Notifications
You must be signed in to change notification settings - Fork 24
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
Fix test failures (can't find executable; CRLF) #29
Conversation
Any update :) |
Not currently - do you have any thoughts or other test cases? I'll work on it as soon as I can. I have been following some of the notifications in other repos and I know this needs to be taken care of. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix! This is really nice. I have posted some questions.
@xuhdev Updated per your comments, and CI tests pass on the linked PRs :) . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, the PR LGTM except my last question as commented. Cheer for the hard work!
Fixes: - editorconfig#28 - The warning at https://ci.appveyor.com/project/xuhdev/editorconfig-core-c/builds/28235086/job/u9ebs7f3b9u3gowk#L1660 Major changes: - Always use add_test(NAME ... COMMAND ...): This is for consistency - add_test(NAME ... COMMAND ...) escapes differently than add_test(<name> <command>...). - Fix backslash escaping: Now that we are using the add_test(NAME ... COMMAND ...) form, backslash escaping works differently. In my tests, backslashes are not collapsed in that form. - Specify `-C Debug` on the `ctest` command line: This permits the Visual Studio generator to run tests.
Related PRs have passed CI tests. Thank you for your kind words! |
Merged. Very cool. Thanks! |
@xuhdev any plan to tag a new release? |
@greut editorconfig/editorconfig#395 I think it's time to formulate a voting about versioning scheme. After that, we should be able to start tagging, along with the spec. |
As requested by @xuhdev - working on fixing #28. See details at #28 (comment) .
@editorconfig/developers Please see "Requirements on cores," below.
Overview
Requirements on cores
EDITORCONFIG_CMD
to=<target name>
rather than a path to the executable. That will cause the tests to get the executable's name from cmake. See, e.g., this example.Corresponding PRs I have been using to test these changes
These are currently draft, and I will submit them formally once this PR is merged.