Understanding results of a Try push can be difficult. I have started writing some documentation on tools to help understand it: https://firefox-source-docs.mozilla.org/testing/treeherder-try/index.html
Specifically I want to call out "Confirm Failure". This runs much faster than a retrigger and yields as strong if not a stronger signal. It runs as tier-3 right now, so you need to view tier-3 jobs in your try push. Currently there are plans to make this more streamlined (and once there it will be tier-2), specifically: * better UI filtering for tasks that don't have a clear signal after running confirm failures * a more automated way to run confirm failure for try pushes (will at least require a bug, most likely a phabricator ID) * other tools for running it easier manually The more these tools are used, the more usability and edge cases can be fixed. -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/179bb0d6-4122-468c-8958-9defb0730d13n%40mozilla.org.
