Angela P Wen

> Now, looks like the tests are failing because `interpreted.json` is trying to be deleted, but a lock on it is being held by another process or something. It has...

Phew, renaming the path worked 😸 so this PR is finally ready for re-review

Hello! Thank you for reporting. I can look into this for you as I authored https://github.com/github/codeql-action/pull/2083. I'd like to understand why `/sys/fs/cgroup/cpuset.cpus` is reporting 1 CPU here: https://github.com/github/codeql-action/blob/dc983b33c32da66f1acc44a1d5ed69d94e9ffb64/src/util.ts#L469. If I...

Ah, I understand why the count is reporting as 1 now. I've put up https://github.com/github/codeql-action/pull/2151 which should address this issue. Thank you!

Is there any downside to adding the fix from https://github.com/github/codeql/commit/6cbf8abf590547e714ada473de66cdeba5cfb010 to all traced languages? If not we can try that out and see how it goes.

Following up — yes, Alex had a PR for exactly that in https://github.com/github/semmle-code/pull/48593 but it had to be reverted because it was failing integration tests on SIP-disabled ARM runners. I...

@jsoref, thanks! Will update now.

Hi @stevehipwell, thank you for reporting this ✨ Do you mind sharing the version of the CodeQL Action you're currently on, as well as the relevant part of your Dependabot...

👋 @stevehipwell thank you for sharing. Our team looked into this and found that there was a mistaken bump to the SHA your workflow is pinned to, `cdcdbb579706841c47f7063dda365e292e5cad7a`, which corresponds...

Thanks for following up @stevehipwell: historically, we've used GitHub releases for the `codeql-action` repo as a way to release the CodeQL bundle, which you'll see in https://github.com/github/codeql-action/releases. CodeQL bundles also...