Fetching SPM from private repository when including CodeQL init step

[einar-notland]

Not sure what causes this. But our Xcode build job just gets stuck at SPM trying to fetch a framework from a private repository when having the CodeQL initialisation step in our workflow.

The SPM fetching works fine for workflows where we do not initialise CodeQL.

The workflow does not fail, it just gets stuck at the place where it is trying to fetch the private repository package. To allow it to fetch this private repo, I use this action to add the credentials: akiojin/store-git-credential-github-action@v1. And this credentials stuff works fine for our normal builds. But in our CodeQL workflow it fails the way I have described, just being stuck at the fetching step.

Anybody have any idea here?

[rvermeulen]

Hi @einar-notland,

Thanks for your question. Is it possible to share the database creation and build tracer logs so we can diagnose what may cause the slowdown?

If this is a private project we may need to find a way to securely share these logs to ensure we do not disclose information.

[einar-notland]

Yeah, I could also try to just find the part you're interested in and try to anonymise it.

But how do I extract what you are interested in. Currently the logs for the workflow just show the SPM fetching logs, like this:
Fetching from https://github.com/[ORG]/[REPO]

[rvermeulen]

Hi @einar-notland, let me inquire if we can provide you with interesting parts to look for in the logs and get back to you.

[einar-notland]

@rvermeulen Did you get the time to investigate this? As stated above, our workflow just gets stuck. And the final line in the log is:
Fetching from https://github.com/[ORG]/[REPO]

Then the job just continues to run until it is force-quitted or time-out after 6 hours.

[smowton]

Could you upload the database directory in its partially-created state? If there's confidential information you wouldn't want visible on this public issue tracker, perhaps you could use Google Drive and share to smowton@github.com?

[coadaflorin]

Hey @einar-notland we noticed that you are using fastlane. Fastlane is not officially supported right now. While scanning when using fastlane does work sometimes, it is known to cause issues. Is it possible to try running a build without fastlane?

[einar-notland]

Tried building directly using xcodebuild, same issue.
Screenshot (redacted details)

[coadaflorin]

Can you ask them to share the information @smowton asked for, please?

[einar-notland]

I did share the information with @smowton
If you give me a google account email, I can share it with you as well.

[redsun82]

Hi @einar-notland sorry for coming back to this so late.

If this is still affecting you, can you try setting CODEQL_TRACER_RELOCATION_EXCLUDE=".*/git" in the environment, to see if that helps?

[einar-notland]

Hi @einar-notland sorry for coming back to this so late.

If this is still affecting you, can you try setting CODEQL_TRACER_RELOCATION_EXCLUDE=".*/git" in the environment, to see if that helps?

@redsun82 Thx for reaching out. The fix you proposed works. We can now finally run CodeQL on our code again.