Can you please raise a support ticket answering the following questions:
Are you are only seeing this issue when a specific user triggers a build?
Is this the only project in which you are seeing this issue?
Can you also confirm that you have tried signing out of CircleCI and logging back in and continuing to see the issue?
Hi there Owen. Thanks for getting back. We since haven’t seen this issue in a while. I wonder if it’s an issue with a PR from a specific fork. Anyway hard to debug and maybe not worth investigation unless it happens a bit more… I’ll let you know if it does.
We started seeing this recently in GitHub - coredns/coredns: CoreDNS is a DNS server that chains plugins … seemingly intermittently in submitted PRs. If I close and re-open a PR that is affected, it usually runs our circleci job successfully. The circleci pipeline error itself however appears to permanently remain in the Task Status, despite subsequent successful runs.