-
Notifications
You must be signed in to change notification settings - Fork 1.5k
updated CI to latest ubuntu and clang #4004
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
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
efeaf4b
updated CI to latest ubuntu and clang
firewave 5abe89a
.clang-tidy: disabled readability-identifier-length warning which we …
firewave fe233cf
clang_tidy.cmake: added `run-clang-tidy-14` as program to look for
firewave dec2cbc
CI-unixish-docker.yml: install the `python3` package for ubuntu instead
firewave eb78d4a
run_more_tests.sh: explicitly use `python3`
firewave ef5c4ef
.clang-tidy: disabled `readability-container-data-pointer` since it h…
firewave 6c279bb
use `PYTHON_INTERPRETER` in `checkCWEEntries` make target
firewave 36eae2f
CI-unixish-docker.yml: install `which` and `python3` packages for CentOS
firewave 6d89ebb
compileroptions.cmake: added workaround for current performance regre…
firewave 99714c5
compileroptions.cmake: force the usage of DWARF 4 for clang-14
firewave f66cf74
fixed some clang-tidy-14 warnings
firewave 14a464a
compileroptions.cmake: disabled Clang warning `-Wbitwise-instead-of-l…
firewave f2ead23
remove matchcompiled source files with `make clean`
firewave a1a5bad
adjusted `PYTHON_INTERPRETER` checks
firewave File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 don't have a very strong opinion but I think we can require python3 for this script. It's not something a normal user will run.
Uh oh!
There was an error while loading. Please reload this page.
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.
As outlined in #3596 I think we can completely drop Python 2.7. We also already switched to the distro versions of Python so the CI coverage also exists. But that is also outlined in the other PR.
Also after this is merged we can hopefully merge #3596 as well and we default to Python 3.x everywhere.
I would give it a release cycle to sink in, adding deprecation warnings to the build at the start of the next dev cycle (2.9) and drop it in the one afterward (2.10).
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.
but I wonder what the motivation is to set PYTHON_INTERPRETER here. isn't it enough to use the shebang as we used to?
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.
You can specify the interpreter when running
make:PYTHON_INTERPRETER=/usr/local/bin/python3.11 makeSo this is done for consistency. It will mainly be necessary for testing and MinGW on Windows if the interpreter is not in the
PATH.Before this change it was done once globally but only with
MATCHCOMPILER=yes. Since that might not be set and we don't want to do it unconditionally I had to replicate this since I was not able to do it in conditional code.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.
As far as I know, until now those that used
checkCweEntrieswas satisfied with the shebang path. It's a script that is used very rarelly.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.
It also fails on platforms like Ubuntu 22.04 where
pythonnot longer exists by default and the shebang is not changed yet. The other way around it would fail if no Python 3 is installed by default like CentOS after the shebang is changed. So this is a required change to make the CI work.