58 bytes, text/x-review-board-request
I needed to clobber OSX builders earlier today to fix a build issue on inbound, so I went to https://api.pub.build.mozilla.org/clobberer/ Somewhat-unrelatedly, buildapi was broken at the time so I couldn't do it until that was sorted out. Once buildapi came back online, I went back to Clobberer to try to clobber Mac builders, so I then selected "mozilla-inbound" from the list of trees. But the only builders shown were linux and windows. I then looked at mozilla-central and saw the same. Fx-team was also the same. Mozilla-aurora still lists OSX builders, as does mozilla-beta. Looking now, Android builders are also missing on trunk, but are present on non-trunk. I went ahead and just landed a CLOBBER touch on inbound to deal with my current build issue, so I'm not immediately blocked on this, but it would be nice to know why they aren't being listed, and to get them listed again.
This is still a problem, any idea what's wrong or how to fix it?
AKi, is this related to your mozharness patch for purge builds?
Probably. http://hg.mozilla.org/integration/mozilla-inbound/diff/f9649610cd9c/testing/mozharness/mozharness/mozilla/purge.py#l1.23 I'll add the self.clobberer() call at http://hg.mozilla.org/integration/mozilla-inbound/diff/f9649610cd9c/testing/mozharness/mozharness/mozilla/purge.py#l1.80 .
Review commit: https://reviewboard.mozilla.org/r/38987/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/38987/
Attachment #8728592 - Flags: review?(catlee)
Yay for aki.
Comment on attachment 8728592 [details] MozReview Request: bug 1254356 - readd self.clobberer() call. r?catlee https://reviewboard.mozilla.org/r/38987/#review35669
Comment on attachment 8728592 [details] MozReview Request: bug 1254356 - readd self.clobberer() call. r?catlee https://reviewboard.mozilla.org/r/38987/#review35675 bug 1254356 - readd self.clobberer() call. r=catlee
Attachment #8728592 - Flags: review+
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.