Temporarily disable "ash" branch after taskcluster migration due to no recent builds
Categories
(Webtools :: Searchfox, task)
Tracking
(Not tracked)
People
(Reporter: asuth, Unassigned)
Details
The "ash" branch is currently breaking the main searchfox indexing run (config.json that contains mozilla-central). I began looking very preliminarily into adding the ability to mark the failure of certain indexing (setup or indexing) runs as non-fatal, but looking into how to weave appropriate error handling into our use of "set -e" made me give up all hope on that. (Various people apparently have created try/catch macrology that looks "neat" for a very specific value of "neat".)
I'm going to remove ash from the config.json for now and we can put it back when it has green builds again. (:peterv did a merge and push, which would have fixed things, but there's some kind of bit-rot that needs to be fixed, as all the builds are red. Plus we're seeing the eternal problem where windows builds just don't seem to be reliably scheduled. Although thankfully emilio corrected our error handling there.)
|
||
Comment 1•6 years ago
|
||
ash is greenish now.
|
Reporter | |
Comment 2•6 years ago
|
||
Disabling PR that got us a successful run: https://github.com/mozsearch/mozsearch-mozilla/pull/62
Reverting PR that just landed: https://github.com/mozsearch/mozsearch-mozilla/pull/63
Note that the windows builds are still queued.. one for 10 hours, one for 3.5 hours. I started to file a taskcluster bug, but it seems like in general the windows builds have actually been healthy and started promptly on the other branches. Something to keep an eye on, though.
Description
•