Manish Goregaokar

(note: won't have time to review this for a few weeks)

This basically exists already. `@homu treeclosed=5` will close the tree for any PR below priority 5. (It can be unset with `treeclosed-`) It will not however interrupt existing builds or...

See https://github.com/servo/homu/pull/87

That seems weird. I'm looking at your settings and don't see anything off. Feels like a misconfiguration -- i don't see this pattern on other homu-using repos -- but I...

Yeah i suspect a problem in your Travis config as well but I looked at the Travis stuff and it all seems fine. Unsure what's happening.

Yeah, makes sense for it to be a homu bug. Don't have the bandwidth right now to investigate it but might be worth logging wherever homu explicitly requests a build.

Yeah I would add a bunch of printfs wherever homu makes decisions regarding triggering builds.

Storing the results in a db is a bunch of work. Doable, but work. Having them get fetched via JS should not be hard. May hit rate limits.

I personally was envisioning a small colored dot that you can hover over to get individual sub-CI statuses. Same thing you see on github, basically.

try should imply clean retry at all times; this is a bug