Skip to content

Overlay: Add QL for QL query to warn about possible non-inlining across overlay frontier #1430

Overlay: Add QL for QL query to warn about possible non-inlining across overlay frontier

Overlay: Add QL for QL query to warn about possible non-inlining across overlay frontier #1430

Triggered via pull request May 27, 2025 10:38
Status Success
Total duration 10m 29s
Artifacts

ql-for-ql-tests.yml

on: pull_request
Matrix: other-os
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
qltest
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.21.3.
qltest
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration - https://docs.github.com/rest
other-os (macos-latest)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.21.3.
other-os (macos-latest)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration - https://docs.github.com/rest
other-os (macos-latest)
gnu-tar 1.35 is already installed and up-to-date. To reinstall 1.35, run: brew reinstall gnu-tar
other-os (windows-latest)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.21.3.
other-os (windows-latest)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration - https://docs.github.com/rest