Confirmed users
1,031
edits
No edit summary |
|||
Line 55: | Line 55: | ||
=== Troubleshooting === | === Troubleshooting === | ||
Leeroy listens to events as they happen with no queue or storage. If a network event is dropped and something gets stuck in a strange state, the only thing you can do is change the sha or open a new PR. There is an issue open on leeroy to change this. Until then, I suggest adding a trivial commit (add some whitespace to your readme) and rerunning, then popping that commit off the PR with a rebase after it passes. | Leeroy listens to events as they happen with no queue or storage. If a network event is dropped and something gets stuck in a strange state, the only thing you can do is change the sha or open a new PR. There is an issue open on leeroy to change this. Until then, I suggest adding a trivial commit (add some whitespace to your readme) and rerunning, then popping that commit off the PR with a rebase after it passes. | ||
There's a bugzilla component for filing problems with Leeroy itself: https://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools&component=Leeroy |