| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
These were supplying CODEQL_EXTRACTOR_GO_BUILD_TRACING=true rather than CODEQL_EXTRACTOR_GO_BUILD_TRACING=on, therefore tracing wasn't being tested.
This is currently broken in CLI versions 2.10.3 and earlier.
|
Rebased on main to address a merge conflict. |
Sorry, something went wrong.
It is enough to pass the checks now that we only use the runner for PR checks.
There was a problem hiding this comment.
Seems reasonable. Thanks for the investigation and fix!
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fix Go tracing tests
We're currently supplying CODEQL_EXTRACTOR_GO_BUILD_TRACING=true rather than the expected CODEQL_EXTRACTOR_GO_BUILD_TRACING=on in the PR checks, therefore tracing isn't being tested.
This PR updates the PR checks to the expected CODEQL_EXTRACTOR_GO_BUILD_TRACING=on and also adds an error if it's set to true. Making true a synonym of on is more difficult than it's worth as the Go autobuilder also looks at this environment variable, so whether true is a synonym or not would depend on the version of the CodeQL CLI.
Fix Go tracing on Windows
After fixing the tests, we discovered a bug with Go tracing on Windows with the Lua tracer. We have a fix here: github/codeql#10147. Until this fix is released, we disable Lua tracing on Windows when analyzing Go.
Merge / deployment checklist