[bug] [ci] Danger hung up on "Pending"
See original GitHub issueDescribe the bug Danger randomly gets hung on a pending state - “Expected, waiting for status to be reported”. This prevents merge since we require this action the pass. The issue can be resolved by rerunning the entire ci workflow, but that shouldn’t be necessary.
To Reproduce Steps to reproduce the behavior:
- Open a PR and see it get hung up
- circle ci console looks like this
yarn danger ci --failOnErrors
yarn run v1.22.4
$ /home/circleci/react-uswds/node_modules/.bin/danger ci --failOnErrors
Skipping Danger due to this run not executing on a PR."
Done in 0.35s.
CircleCI received exit code 0
- Rerunning the worflow resolves the issue and things work the second time
Expected behavior Want danger to run and complete the first time 😅
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Troubleshooting CI/CD - GitLab Docs
CI /CD troubleshooting rails console commands · Cancel stuck pending pipelines · Try merge request integration · Validate the .gitlab-ci.yml file · Disable ......
Read more >Github pull request - Waiting for status to be reported
It will re-trigger all the checks you have in CI. ... It's working for me: close the stuck pull request and reopen it....
Read more >CHANGELOG - Danger.systems
Bitbucket Cloud: Fix bug when Danger updating inline comment with summary comment. ... Before that, Danger on GitHub Actions is stuck at v5.0.0-beta-24....
Read more >Windows 7 Ultimate SP1 installation fails with error code ...
if i try to enter in safe mode, i get stuck on driver loading (last ... Tried renaming pending.xml, rebooted & system hangs...
Read more >Role of Confidential Informants - Special Report
Bulger was tipped off by FBI Special Agent John Connolly to his pending arrest ... A proposed informant may remain in "suitability inquiry...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The danger code says we should enable “Only Build pull requests”. We do not have that set in Circle right now. I’m inclined to turn that on.
I closed my PR and then made a new branch and pushed it up. There wasn’t a PR associated with it, but the pipeline in CircleCI still started. I intentionally didn’t create the PR right away.
The results in CircleCI show that the danger checks were skipped.
I think this is the most likely explanation: when PRs are opened after the CI run finishes, they don’t have danger results.
I’m not sure there’s a good way to fix this.