The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum and provide the following failing analysis ID: “ffdee664-efe0-45d0-b585-2334cbd74c87”.
Please contact me to advise what is causing the failure.
Hi,
Welcome to the community!
Can you provide the approximate timestamp of this failure? Having that will make it easier to find in our logs.
Thx,
Ann
Thanks for replying. It was shortly before I created this post which was 3:02 PM EST. So let’s say around 2:30 PM EST
Hi,
Thanks for that! I’ve flagged this for the folks with log access.
Ann
Thanks. I hadn’t mentioned initially, this is during the first automated analysis run for a new project.
Hi, I’m following up on this again. When can we expect to hear back?
Hi,
Unfortunately, I can’t answer that.
Ann
That’s too bad, thanks G Ann Campbell.
Log access team - Any response from the the folks with log access?
Hello @sqube
We found the trace of the error, but we are still unable to understand it.
Our automatic analysis is simply trying to checkout you project source code, using the following Git commands:
mkdir /tmp/somerandomfoldername
git -C /tmp/somerandomfoldername init
git -C /tmp/somerandomfoldername remote add origin https://github.com/yourorg/your-repo
git -C /tmp/somerandomfoldername fetch --prune --no-recurse-submodules origin +refs/heads/develop:refs/remotes/origin/develop
The last command is failing with this error, that we can’t really explain as we normally don’t have concurrent analysis happening on the same filesystem:
error: cannot lock ref 'refs/remotes/origin/develop': unable to create directory for .git/refs/remotes/origin/develop
Would you mind trying to run those commands on your side to see if you can reproduce the same issue? We can’t do it on our side as your repository is private.
Thanks!