Wonder if autoland's backout rate will go up when autoland is detached from
mozreview (letting someone autoland directly from bugzilla is in the plans,
I believe).
On Tue, Mar 7, 2017 at 4:47 AM, Carsten Book wrote:
> Hi,
>
> i agree with Sebastian - the integration of
I don't believe that's a workable situation. At the moment, the policy is that
every new intermittent failure gets a bug filed for the purpose of tracking it.
There's talk (and has been for at least a year or two, now) that work will
begin on OrangeFactor version 2, where intermittent failures
The Treeherder devs have deployed a hotfix that appears to have fixed up
the responsiveness issues, so I've reopened the trees.
On Mon, Jul 18, 2016 at 5:05 PM, Wes Kocher <wkoc...@mozilla.com> wrote:
>
> The DB issues that popped back up again from bug 1286942 have been
> resolv
The DB issues that popped back up again from bug 1286942 have been
resolved, and all non-trunk trees have been reopened.
Treeherder responsiveness has been an issue all day (bug 1287501), which is
keeping the trunk trees closed, since I can't easily tell if jobs are
broken. The responsiveness
Additional DB issues have popped up today, so trees are again closed. We
are re-using bug 1286942 as the tracking bug.
On Fri, Jul 15, 2016 at 2:59 AM, Carsten Book wrote:
> Hi,
>
> we currently have a complete tree closure due to Buildbot DB Issues.
>
> The Teams working on
What if the query was changed to only count bugs resolved 'fixed'? I
believe all of the inactive intermittent bugs get closed as worksforme or
invalid?
On Mon, Sep 28, 2015 at 10:45 AM, Ehsan Akhgari
wrote:
> On 2015-09-28 7:26 AM, Carsten Book wrote:
>
>> 3. Statistics
This is great. Thanks for this!
Wes
On Mon, Sep 28, 2015 at 5:31 PM, Ed Morley wrote:
> Currently whenever a sheriff or developer classifies an intermittent
> failure on Treeherder with a bug number, a comment is left on that bug for
> every occurrence.
>
> We're going to
7 matches
Mail list logo