Repository navigation
Add compiler warning tracking tooling failure remediation guidance #1364
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
Changes from 1 commit
780b372
3a6d880
db3ed48
cf4d962
f6395aa
3aeb0c9
6ca97f8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,19 +1,19 @@ | ||||||
| .. warnings: | ||||||
|
|
||||||
| ================================= | ||||||
| Compiler Warning Tracking Tooling | ||||||
| ================================= | ||||||
| Tools for tracking compiler warnings | ||||||
| ==================================== | ||||||
|
|
||||||
| The compiler warning tracking tooling is intended to alert developers to new | ||||||
| compiler warnings introduced by their contributions. The tooling consists of | ||||||
| python script which is ran by a few GitHub Actions worksflows. Currently these | ||||||
| Python script which is ran by a few GitHub Actions workflows. These | ||||||
|
hugovk marked this conversation as resolved.
Outdated
|
||||||
| GitHub Actions jobs run the warning checking tooling: | ||||||
|
|
||||||
| - Ubuntu/Build and Test | ||||||
| - macOS/Build and Test | ||||||
|
|
||||||
| The help text for the `Tools/build/check_warnings.py` is as follows: | ||||||
| :: | ||||||
| The help text for the :cpy-file:`Tools/build/check_warnings.py` is as follows: | ||||||
|
|
||||||
| .. code-block:: text | ||||||
|
|
||||||
| usage: check_warnings.py [-h] | ||||||
| -c COMPILER_OUTPUT_FILE_PATH | ||||||
|
|
@@ -46,24 +46,24 @@ compiler output type to see a list of unique warnings. | |||||
|
|
||||||
| .. _warning-check-failure: | ||||||
|
|
||||||
| What To Do If Warning Check Fails GitHub CI | ||||||
| What to do if a warning check fails GitHub CI | ||||||
| ------------------------------------------- | ||||||
|
|
||||||
| The warning check tooling will fail if the compiler generates more or less | ||||||
| warnings than expected for a given source file as defined in the platform | ||||||
| specific warning ignore file. The warning ignore file is either | ||||||
| `Tools/build/.warningignore_ubuntu` or `Tools/build/.warningignore_macos` | ||||||
| warnings than expected for a given source file as defined in the | ||||||
| platform-specific warning ignore file. The warning ignore file is either | ||||||
| :cpy-file:`Tools/build/.warningignore_ubuntu` or :cpy-file:`Tools/build/.warningignore_macos` | ||||||
| depending on the platform. | ||||||
|
|
||||||
| If warning check fails with: | ||||||
| If a warning check fails with: | ||||||
|
|
||||||
| 1. Unexpected Warnings | ||||||
| a. Attempt to refactor the code to avoid the warning. | ||||||
| b. If it is not possible to avoid the warning document in the PR why it is | ||||||
| * Unexpected Warnings | ||||||
|
hugovk marked this conversation as resolved.
Outdated
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I kept the language the same but fixed the capitalization. The reason being that the script actually labels warnings as "Unexpected improvements" and "Unexpected warnings" |
||||||
| * Attempt to refactor the code to avoid the warning. | ||||||
| * If it is not possible to avoid the warning document in the PR why it is | ||||||
| reasonable to ignore and add the warning to the platform specific | ||||||
|
hugovk marked this conversation as resolved.
Outdated
|
||||||
| warning ignore file. If the file exists in the warning ignore file | ||||||
| increment the count by the number of new introduced warnings. | ||||||
|
hugovk marked this conversation as resolved.
Outdated
|
||||||
| 2. Unexpected Imrpovements (Less Warnings) | ||||||
| a. Document in the PR that the change reduces the number of compiler | ||||||
| * Unexpected Imrpovements (Less Warnings) | ||||||
|
hugovk marked this conversation as resolved.
Outdated
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I kept the language the way it was but fixed the capitalization, same reason as above the script actually labels specific warnings as such. |
||||||
| * Document in the PR that the change reduces the number of compiler | ||||||
| warnings. Decrement the count in the platform specific warning | ||||||
|
hugovk marked this conversation as resolved.
Outdated
|
||||||
| ignore file or remove the file if the count is now zero. | ||||||
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.
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.
changed to about