using https://treestatus.mozilla.org/mozilla-inbound, I looked at the reasons for tree closures (usually associated with backouts), going back to 50 status messages, I found: 38 test issues 14 build issues 9 infrastructure issues 2 other issues
Note, some of these closures had >1 issue documented. Questions to ask would be: * How many of these build issues would have been resolved by a developer building locally? * How many of these test issues would have been resolved by a developer running a simple smoketest (i.e. <5 minutes)? I agree that running on try server over and over again is just pushing the resource problem from a managed tree to an unmanaged tree. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
