(In reply to Emilio Cobos Álvarez (:emilio) from comment #1) > This is adding Talos tests, so I think this is expected unless I'm missing something? I thought we only tracked the individual tests nowadays? > > Anyhow I think this is INVALID. Actually that's not right. If you look at this graph, revision 455228c96302 was caused by the same bug as ff3ba7a16c21 (they have only one bug in common and the evolution of the graph is similar) which we know was caused by 1480146. I am not saying this is not expected, I'm saying that this is not INVALID. I found 2 other alerts showing what this shows. So unless you have another explaination, I'm changing the status to WON'T FIX.
Bug 1575157 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1) > This is adding Talos tests, so I think this is expected unless I'm missing something? I thought we only tracked the individual tests nowadays? > > Anyhow I think this is INVALID. (In reply to Alexandru Ionescu :alexandrui from comment #2) > Yeah, looking on the other platforms reveals that some other revision caused this. Thanks! Actually that's not right. If you look at this graph, revision 455228c96302 was caused by the same bug as ff3ba7a16c21 (they have only one bug in common and the evolution of the graph is similar) which we know was caused by 1480146. I am not saying this is not expected, I'm saying that this is not INVALID. I found 2 other alerts showing what this shows. So unless you have another explaination, I'm changing the status to WON'T FIX.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1) > This is adding Talos tests, so I think this is expected unless I'm missing something? I thought we only tracked the individual tests nowadays? > > Anyhow I think this is INVALID. (In reply to Alexandru Ionescu :alexandrui from comment #2) > Yeah, looking on the other platforms reveals that some other revision caused this. Thanks! Actually that's not right. If you look at this graph, revision 455228c96302 was caused by the same bug as ff3ba7a16c21 (they have only one bug in common and the evolution of the graph is similar) which we know was caused by 1480146. I am not saying this is not expected, I'm saying that this is not INVALID. I found 2 other alerts showing what this shows. So unless you have another explaination, I'm changing the status to WON'T FIX.