1364373 - Treeherder should inform about the day count of the specific intermittent failure

Status: RESOLVED DUPLICATE of bug 1367362

(Tree Management :: Treeherder, defect)

Description

[Carsten Book [:Tomcat]]

In some cases of our daily work we have sometimes perma failures that hide under existing bugs like as example something regress and goes perma failure but its not instantly noticed because 

-> there is an existing bug (maybe even some time old)
-> someone filed a new Bug and everyone thinks its a intermittent issue because of the filed bug

this can especially between shift changes of sheriffs be a problem.

To make our work better i was thinking of having some indication how much failures of this specific test/error has been during the last 24 hours

like 1147271 Intermittent Windows build subprocess.CalledProcessError: Command '['ssh', '-o', 'IdentityFile=/c/Users/cltbld/.ssh/ffxbld_rsa', '-o', 'BatchMode=yes', '[e-mail]', 'mktemp -d']' returned non-zero exit status 255 - and also some indication like 5 failures of this today


this would make our job much easier, better and improve the quality !

Comment 1

[Carsten Book [:Tomcat]]

ed mentioned on irc yesterday that this has to wait/depend on orangefactor v2 .

Ed do you know any timeplan/eta for the v2 of orangefactor ?

Comment 2

[Ed Morley [:emorley]]

I would guess Q3-Q4 - see bug 1356410.