Test config with queries as list of strings #10607
codeql.yml
on: push
check-codeql-versions
33s
Matrix: analyze-other
Matrix: analyze-javascript
Annotations
7 errors and 23 warnings
|
analyze-javascript (ubuntu-24.04)
Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.23.2/x64/codeql/codeql database init --force-overwrite --db-cluster /home/runner/work/_temp/codeql_databases --source-root=/home/runner/work/codeql-action/codeql-action --calculate-language-specific-baseline --extractor-include-aliases --sublanguage-file-coverage --language=javascript --codescanning-config=/home/runner/work/_temp/user-config.yaml". Exit code was 2 and error was: A fatal error occurred: Config file supplied is not valid
(eventual cause: MismatchedInputException "Cannot construct instance of `com.semmle.cli2.database.UserConfig$QuerySpec` (al..."). See the logs for more details.
|
|
analyze-javascript (ubuntu-22.04)
Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.23.2/x64/codeql/codeql database init --force-overwrite --db-cluster /home/runner/work/_temp/codeql_databases --source-root=/home/runner/work/codeql-action/codeql-action --calculate-language-specific-baseline --extractor-include-aliases --sublanguage-file-coverage --language=javascript --codescanning-config=/home/runner/work/_temp/user-config.yaml". Exit code was 2 and error was: A fatal error occurred: Config file supplied is not valid
(eventual cause: MismatchedInputException "Cannot construct instance of `com.semmle.cli2.database.UserConfig$QuerySpec` (al..."). See the logs for more details.
|
|
analyze-javascript (macos-15)
Encountered a fatal error while running "/Users/runner/hostedtoolcache/CodeQL/2.23.2/arm64/codeql/codeql database init --force-overwrite --db-cluster /Users/runner/work/_temp/codeql_databases --source-root=/Users/runner/work/codeql-action/codeql-action --calculate-language-specific-baseline --extractor-include-aliases --sublanguage-file-coverage --language=javascript --codescanning-config=/Users/runner/work/_temp/user-config.yaml". Exit code was 2 and error was: A fatal error occurred: Config file supplied is not valid
(eventual cause: MismatchedInputException "Cannot construct instance of `com.semmle.cli2.database.UserConfig$QuerySpec` (al..."). See the logs for more details.
|
|
analyze-javascript (macos-14)
Encountered a fatal error while running "/Users/runner/hostedtoolcache/CodeQL/2.23.2/arm64/codeql/codeql database init --force-overwrite --db-cluster /Users/runner/work/_temp/codeql_databases --source-root=/Users/runner/work/codeql-action/codeql-action --calculate-language-specific-baseline --extractor-include-aliases --sublanguage-file-coverage --language=javascript --codescanning-config=/Users/runner/work/_temp/user-config.yaml". Exit code was 2 and error was: A fatal error occurred: Config file supplied is not valid
(eventual cause: MismatchedInputException "Cannot construct instance of `com.semmle.cli2.database.UserConfig$QuerySpec` (al..."). See the logs for more details.
|
|
analyze-javascript (macos-13)
Encountered a fatal error while running "/Users/runner/hostedtoolcache/CodeQL/2.23.2/x64/codeql/codeql database init --force-overwrite --db-cluster /Users/runner/work/_temp/codeql_databases --source-root=/Users/runner/work/codeql-action/codeql-action --calculate-language-specific-baseline --extractor-include-aliases --sublanguage-file-coverage --language=javascript --codescanning-config=/Users/runner/work/_temp/user-config.yaml". Exit code was 2 and error was: A fatal error occurred: Config file supplied is not valid
(eventual cause: MismatchedInputException "Cannot construct instance of `com.semmle.cli2.database.UserConfig$QuerySpec` (al..."). See the logs for more details.
|
|
analyze-javascript (windows-2025)
Encountered a fatal error while running "C:\hostedtoolcache\windows\CodeQL\2.23.2\x64\codeql\codeql.exe database init --force-overwrite --db-cluster D:\a\_temp\codeql_databases --source-root=D:\a\codeql-action\codeql-action --calculate-language-specific-baseline --extractor-include-aliases --sublanguage-file-coverage --language=javascript --codescanning-config=D:\a\_temp\user-config.yaml". Exit code was 2 and error was: A fatal error occurred: Config file supplied is not valid
(eventual cause: MismatchedInputException "Cannot construct instance of `com.semmle.cli2.database.UserConfig$QuerySpec` (al..."). See the logs for more details.
|
|
analyze-javascript (windows-2022)
Encountered a fatal error while running "C:\hostedtoolcache\windows\CodeQL\2.23.2\x64\codeql\codeql.exe database init --force-overwrite --db-cluster D:\a\_temp\codeql_databases --source-root=D:\a\codeql-action\codeql-action --calculate-language-specific-baseline --extractor-include-aliases --sublanguage-file-coverage --language=javascript --codescanning-config=D:\a\_temp\user-config.yaml". Exit code was 2 and error was: A fatal error occurred: Config file supplied is not valid
(eventual cause: MismatchedInputException "Cannot construct instance of `com.semmle.cli2.database.UserConfig$QuerySpec` (al..."). See the logs for more details.
|
|
check-codeql-versions
Resource not accessible by integration - https://docs.github.com/rest
|
|
check-codeql-versions
Resource not accessible by integration - https://docs.github.com/rest
|
|
check-codeql-versions
Resource not accessible by integration - https://docs.github.com/rest
|
|
check-codeql-versions
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.23.2.
|
|
check-codeql-versions
Resource not accessible by integration - https://docs.github.com/rest
|
|
check-codeql-versions
Resource not accessible by integration - https://docs.github.com/rest
|
|
check-codeql-versions
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.23.2.
|
|
check-codeql-versions
Resource not accessible by integration - https://docs.github.com/rest
|
|
check-codeql-versions
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
|
|
analyze-javascript (ubuntu-24.04)
Debugging artifacts are unavailable since the 'init' Action failed before it could produce any.
|
|
analyze-javascript (ubuntu-24.04)
2 diagnostic(s) could not be written to the database and will not appear on the Tool Status Page.
|
|
analyze-javascript (ubuntu-22.04)
Debugging artifacts are unavailable since the 'init' Action failed before it could produce any.
|
|
analyze-javascript (ubuntu-22.04)
2 diagnostic(s) could not be written to the database and will not appear on the Tool Status Page.
|
|
analyze-javascript (macos-15)
Debugging artifacts are unavailable since the 'init' Action failed before it could produce any.
|
|
analyze-javascript (macos-15)
2 diagnostic(s) could not be written to the database and will not appear on the Tool Status Page.
|
|
analyze-javascript (macos-14)
Debugging artifacts are unavailable since the 'init' Action failed before it could produce any.
|
|
analyze-javascript (macos-14)
2 diagnostic(s) could not be written to the database and will not appear on the Tool Status Page.
|
|
analyze-javascript (macos-13)
Debugging artifacts are unavailable since the 'init' Action failed before it could produce any.
|
|
analyze-javascript (macos-13)
2 diagnostic(s) could not be written to the database and will not appear on the Tool Status Page.
|
|
analyze-javascript (windows-2025)
Debugging artifacts are unavailable since the 'init' Action failed before it could produce any.
|
|
analyze-javascript (windows-2025)
2 diagnostic(s) could not be written to the database and will not appear on the Tool Status Page.
|
|
analyze-javascript (windows-2022)
Debugging artifacts are unavailable since the 'init' Action failed before it could produce any.
|
|
analyze-javascript (windows-2022)
2 diagnostic(s) could not be written to the database and will not appear on the Tool Status Page.
|