Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Compilation warnings #374

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

Open
amdoku wants to merge 8 commits into nodejs:main
base: main
Choose a base branch
Loading
from amdoku:compilation-warnings
Open

Compilation warnings #374

amdoku wants to merge 8 commits into nodejs:main from amdoku:compilation-warnings

Conversation

@amdoku
Copy link

@amdoku amdoku commented Oct 3, 2020

When compiling with gcc-10.2.0 there are some warnings emitted.

The unit tests were failing when using gdb-9.2 and lldb-10.0.1 as the line would change from

error: error: use of undeclared identifier 'invalid_expr'

to

error: error: <user expression 3>:1:1: use of undeclared identifier 'invalid_expr'

This relaxes the test just enough to also work with older versions of gdb & lldb where this location information would not be included.

amdoku added 8 commits October 3, 2020 21:41
When compiling with gcc-10.2.0 this would emit a warning
When compiling under gcc-10.2.0 this line would emit a warning
When compiling under gcc-10.2.0 this would emit a warning
When compiling under gcc-10.2.0 this would emit a warning
By escaping the '?' it will no longer be detected as a trigraph.
When compiling all warnings will now be treated as an error, preventing
potentially misbehaving code from making it onto master.
When executing tests with gdb-9.2 and lldb-10.0.1 the tests would fail.
Relaxing the error assertion to only check for the warning itself, not
the location fixes the test.
Copy link

codecov-commenter commented Oct 3, 2020
edited
Loading

Codecov Report

Attention: Patch coverage is 71.42857% with 2 lines in your changes missing coverage. Please review.

Project coverage is 79.00%. Comparing base (4b868f7) to head (9030cd7).
Report is 54 commits behind head on main.

Files with missing lines Patch % Lines
src/llscan.cc 50.00% 1 Missing ⚠️
src/printer.cc 66.66% 1 Missing ⚠️
Additional details and impacted files
@@ Coverage Diff @@
## main #374 +/- ##
==========================================
- Coverage 79.53% 79.00% -0.54% 
==========================================
 Files 33 33 
 Lines 4744 4743 -1 
==========================================
- Hits 3773 3747 -26 
- Misses 971 996 +25 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /