-
Notifications
You must be signed in to change notification settings - Fork 64
Implement OutOfBounds package #281
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
Conversation
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.
Overall looks good, just some refactoring comments and a few possible missing cases.
I've refactored |
/test-performance |
/test-performance |
🏁 Beep Boop! Performance testing for this PR has been initiated. Please check back later for results. Note that the query package generation step must complete before testing will start so it might be a minute. |
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.
@kraiouchkine -- I think this is going to require some performance work. It's currently running at about double the baseline: https://github.com/github/codeql-coding-standards-release-engineering/actions/runs/4638642279
cc @lcartey
@jsinglet Running the MISRA-C and CERT query-suites does not yield anything out of the ordinary. Could it be your performance testing having a one-off fluke or perhaps something else causing the issue? |
I tried running
Update -- ok so I looked deeper and it appears the problem is with a MISRA query, NOT a CERT query. I didn't realize it but it never even reaches CERT before timing out. I'll let you know when I find it... |
🏁 Beep Boop! Performance testing complete! See below for performance of the last 3 runs vs your PR. Times are based on predicate performance. You can find full graphs and stats in the PR that was created for this test in the release engineering repo.
🏁 Below are the slowest predicates for the last 2 releases vs this PR.
|
@kraiouchkine -- Ok, I tracked it down and the problem query is.... |
@kraiouchkine it looks like you don't have this change https://github.com/github/codeql-coding-standards/blob/rc/2.16/c/misra/src/rules/RULE-7-4/StringLiteralAssignedToNonConstChar.ql <--- release version https://github.com/kraiouchkine/codeql-coding-standards/blob/OutOfBounds/c/misra/src/rules/RULE-7-4/StringLiteralAssignedToNonConstChar.ql <-- your version My suggestion is to update your fork to be in sync with the mergeback I just did into You'll need to first merge this PR or cherry pick that change: #293 |
/test-performance |
🏁 Beep Boop! Performance testing for this PR has been initiated. Please check back later for results. Note that the query package generation step must complete before testing will start so it might be a minute. |
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.
LGTM. Once the performance numbers are in we can officially merge 🚀
🏁 Beep Boop! Performance testing complete! See below for performance of the last 3 runs vs your PR. Times are based on predicate performance. You can find full graphs and stats in the PR that was created for this test in the release engineering repo.
🏁 Below are the slowest predicates for the last 2 releases vs this PR.
|
Incorporate in my review
Description
This pull request implements the C OutOfBounds package.
Change request type
.ql
,.qll
,.qls
or unit tests)Rules with added or modified queries
Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:
If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?
🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.
Reviewer: Confirm that either a change note is not required or the change note is required and has been added.
Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
Reviewer
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.