-
Notifications
You must be signed in to change notification settings - Fork 60
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 ERROR M310 when directory name starts with . #137
Conversation
I think there is an issue in Codecov tool.... |
Yes, the CodeCoverage seems to be not properly configured. We need to check. Can we add some tests for this function?
|
af44a47
to
03685f2
Compare
I think it's done :-)
With only the commit with the new test:
With the patch:
|
Looks promising. I think we could add a unit test in addition to the integration test. |
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.
The coverage reports turns out that the code range under discussion is not properly hit by the provided tests.
<component Cclass="TestClass" Cgroup="TestGlobal" Cversion="1.0.0" condition="Test_Condition"> | ||
<description>TestGlobal</description> | ||
<files> | ||
<file category="source" name=".Files/test1.c"/> |
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.
What are we trying to test here? Filenames starting with a .
should be legal. At least on unix-like systems such files/directories are considered "hidden".
Didn't we discuss (and test) for names starting with ./
? I.e., the unix-like shortcut for "current working directory"?
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.
Yes, the intention is to support these "hidden" elements.
At least ".directory" should be accepted as we plan to use it to collect all the files an end-user does not really need to "see".
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.
Okay, so this test actually does not verify the removal of ./
prefixes, intentionally. So we definitively need to add some more tests, probably unit tests, to really cover the implementation.
Any update ? |
What can we do about the codecov issue blocking the merge ? |
@JonatanAntoni any update ? |
We need to provide more tests to be sure the function does what is expected. Cheers, |
Done |
@jeromecoutant, after merging #262 please consider rebasing this PR to keep contributing your integration test. Actually, we should already have everything covered with the unit tests but the additional integ test would not harm. |
Codecov Report
@@ Coverage Diff @@
## main #137 +/- ##
=======================================
Coverage 66.60% 66.60%
=======================================
Files 24 24
Lines 4734 4734
=======================================
Hits 3153 3153
Misses 1581 1581
Flags with carried forward coverage won't be shown. Click here to find out more. |
Fix #110
See #110 (comment)
@thorstendb-ARM