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.
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
Enable GitHub CodeQL static analysis in CI #693
Enable GitHub CodeQL static analysis in CI #693
Changes from 23 commits
720b103
8ba3a3c
6e7e1f8
f374231
283da42
095d8dc
f7f630a
6270844
e50c544
466cb83
c52963c
faecb38
92ec224
18e6e9d
7e315fc
083cdb0
f173fbe
a077699
922fffb
3905849
e54a713
a07d6c1
4a74f37
83a007d
83c994e
d9096ac
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This step produces the following warning:
The functionality-tests job has a
sudo apt-get --quiet=2 install libtool-bin
step. Other jobs, including this one, rely on build-dep. Evidently, build-dep does not install the libtool binary. The above warning is probably harmless -- the tests succeeded, but we should either install libtool-bin or adjust bootstrap.sh so that it does not trigger that warning. Otherwise, (when the test fails for some other reason,) folks may suspect that the above warning is important/relevant.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.
This is a bug in bootstrap.sh. The warning has shown up on every Linux bootstrap.sh execution since a decade ago without causing the cited confusion. It is out of scope for this PR.
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.
The warning has already caused the cited problems -- I spent time adjusting the now-official workflow configuration to install the tools necessary to eliminate that warning when the builds were failing for other reasons. You do not have to fix or work around this bug, of course, but rejecting the very existence of the problem only wastes time.