-
Notifications
You must be signed in to change notification settings - Fork 675
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
apply clang-format to Tests
#1456
Conversation
61c6d59
to
fafe143
Compare
It's weird. I checked the modification of
|
Does it work for you locally? |
No, it doesn't. It's weird, as the code shouldn't make any difference of the logic. |
bf9a046
to
a32c83d
Compare
|
||
// clang-format off |
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.
don't know why, but seems the formatting of this part will break the tests.
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 the diference between before and after clang-format ?
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.
like this: #define<tab>SEPARATOR '\\'
@@ -6,343 +6,342 @@ | |||
#include <cstring> | |||
#include <sstream> | |||
|
|||
PTF_TEST_CASE(Asn1DecodingTest) | |||
PTF_TEST_CASE(Asn1DecodingTest){ // Context specific |
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.
Indentation formatting is all messed up here.
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.
true, let me fix it.
@seladb ready for review. |
This reverts commit 815531e.
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.
I only reviewed 14 files, but wanted to post my comments so far
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #1456 +/- ##
==========================================
- Coverage 82.09% 80.60% -1.50%
==========================================
Files 273 273
Lines 43551 44647 +1096
Branches 9340 9305 -35
==========================================
+ Hits 35755 35987 +232
- Misses 7207 8069 +862
- Partials 589 591 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
I reviewed 36 / 68 files so far, sharing a few more comments
@tigercosmos CI fails after these changes, can you take a look? |
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.
@tigercosmos I finished reviewing all changes in this PR. Please find a few last comments (plus previous comments that weren't fixed yet). Once we fixed them we should be good to merge this PR
@tigercosmos I have no idea why Codecov includes the test in the test coverage report, I'm sure it wasn't like that before and I'm not sure what's changed 😕 |
Not checked recent changes but it is possible to add ignore rule to codecov.yml https://docs.codecov.com/docs/ignoring-paths#:~:text=You%20can%20use%20the%20top,will%20be%20skipped%20during%20processing. |
@seladb Thanks for your patient review! |
part of #1248