-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Error: Command failed: df -Pk when using macos-14 runners (macos-latest) #16948
Comments
May I ask which version of CodeQL Action you are using? We have previously fixed a similar-looking issue, so it might be sufficient for you to upgrade to the newest version. |
Hi @ginsbach, the workflow in question is using v3 of The build itself is a direct call to XCode: |
👋 thank you for the report @ebickle. The warning about That said, the following lines look like a new issue with the build tracer. We've raised it with the appropriate team internally! |
Hi @ebickle , any chance you could rerun your workflow in debug mode and provide the debug artifact to us? If it contains sensitive data, reach out to github support to privately send it to us, otherwise attaching it on this issue is also fine. |
@criemen I've uploaded the raw debug logs over at https://support.github.com/ticket/personal/0/2886802 |
@ebickle Can you upload the debug artifact, not the debug logs? The codeql-action should produce a debug artifact. If that contains too much confidential data, I'm mostly interested in the |
@criemen Artifacts attached now too! |
Thanks, that was very helpful! We're discussing the problem and possible solutions internally and will get back to you. |
Thanks to @criemen we have a better understanding of the problem related to the build tracer here. We'll work on a fix in the CodeQL Action and update here when we have one! |
👋 we've just released |
Still seeing issues on my side, but different warnings and errors. I've tossed the details into support ticket # 2886802. It occurs when running |
Got it — I see, the |
github/codeql-action#2441 should have the fix in! |
@angelapwen we're also seeing this issue when running
For context this is on an internal Azure DevOps project, feel free to ping me on Teams if you need details. |
Thanks for checking in @akoeplinger — the build tracer fix would likely be much more complex and is not currently scheduled. I recommend stop running the command for now (on MacOS ARM machines) until the work is able to be prioritized. I believe there are some established Microsoft/CodeQL lines of support/requests. Depending on how important running the command is for you, you could raise the issue there to be prioritized as well. |
That did the trick! Tested against @main and everything looks clear now. Thanks! |
Perfect, thank you for letting us know! I'll kick off a release to get it into |
@angelapwen there is https://portal.microsofticm.com/imp/v5/incidents/details/532165079/summary but not sure if there are other open support tickets as that one is still in Triage status. Also my understanding is that this will happen for every platform binary which is arm64e so it'd probably be good to have a public tracking issue. I tried removing |
After GitHub migrated the
macos-latest
label to MacOS 14 (from 12) we noticed the following warning in our CodeQL logs:There isn't too much to the workflow up until that point - it runs
actions/checkout
,pod install
, thengithub/codeql-action/init
withlanguages:swift
on arunner: macos-latest
.As a double check, I cleared all of the GitHub workflow caches and verified I see "Did not find CodeQL tools version 2.17.6 in the toolcache" in the build output.
The text was updated successfully, but these errors were encountered: