homu
homu copied to clipboard
servo
A bot that integrates with GitHub and your favorite continuous integration service
https://github.com/servo/servo/pull/24668#issuecomment-554482397 is an example of a comment that unintentionally triggered a full try job.
There's a bunch of duplicated logic that it would be nice to merge somehow.
It leads to a URL that starts with https://build.servo.org:54856/callback and this times out. If I manually edit the URL to point to https://build.servo.org/homu/callback then it succeeds. It's not clear from...
We already display a comment to inform the user that the trychooser is unknown; I'm unconvinced that we should go ahead and do a full try run as well.
There are two uses of `res` in https://github.com/servo/homu/blob/dfefeb72f13747113e03a826644827db11a5ebdf/homu/main.py#L581-L593 that can trigger exceptions if the repo does not use buildbot.
When using the status API with local git commands, homu can avoid retesting if the previous status result is successful and the base master commit is unchanged. The new changes...
After responding to review comments, a PR might sit in `S-waiting-on-author` until someone from triage notices that the author has responded to the comments. It would be nice if there...
Recent discussion brought up suggestions for [optimistic parallel testing](https://internals.rust-lang.org/t/some-thoughts-on-improving-ci-infrastructure/4869/21?u=eh2406). We should look into allowing these features. I was going to start experimenting tonight, but @edunham mentioned incoming refactorings. So I...
