That’s correct, yeah.  If you don’t have a push where it’s failed already, then 
it won’t show in the Test Centric UI.  Though I’ll write up a bug to explore 
adding this functionality.  Perhaps there’s a way to mine Active Data to get 
this.

-Cam

> On Sep 14, 2017, at 9:05 AM, Gijs Kruitbosch <gkruitbo...@mozilla.com> wrote:
> 
> This only works once you have a run that failed the test you're interested 
> in, right? There's no way to tell the test-centric UI "find me the chunk for 
> test with name X".
> 
> ~ Gijs
> 
> On 14/09/2017 16:55, Cameron Dawson wrote:
>> Marco—  I don’t know of a way to do exactly that yet.  But that is in the 
>> roadmap for the Test-based UI in Treeherder.  And the existing UI may help 
>> you there.
>> 
>> On any push, click the down arrow (Action Menu) at the far right of the push 
>> status line and select “Experimental: Test-Centric UI”
>> From there you can see the list of tests that failed for that push (at this 
>> time, only for tests that log with the structured logging, but they include 
>> Mochitest)
>> For each test, you’ll see a link to the chunk back in Treeherder where that 
>> test ran.  So you can go BACK to Treeherder to do your retrigger there.  
>> This side-UI will be moving back into the main Treeherder repo soon, so 
>> you’ll be able to trigger directly from there at some point.
>> 
>> I realize this workflow is a but cumbersome, but perhaps better than poring 
>> through logs.  :)
>> 
>> I’m actively working on this UI, so please give me any feedback you have in 
>> the form of bugs or in #treeherder.
>> 
>> -Cam
>> 
>> 
>>> On Sep 14, 2017, at 8:48 AM, Marco Bonardo <mbona...@mozilla.com> wrote:
>>> 
>>> When I need to retrigger a mochitest-browser test multiple times (to
>>> investigate an intermittent), often I end up running all the
>>> mochitest-browser tests, looking at every log until I find the chunk
>>> where the test is, and retrigger just that chunk. The chunk number
>>> changes based on the platform and debug/opt, so it's painful.
>>> Is there a way to trigger only the chunk that will contain a given
>>> test, so I can save running all of the other chunks?
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "firefox-ci" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to firefox-ci+unsubscr...@mozilla.com.
>>> To post to this group, send email to firefox...@mozilla.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/a/mozilla.com/d/msgid/firefox-ci/CAPDqYT151ETZSGM83Wo_jdpSj1bHhs57eTpah4bE5PE2BM9ckQ%40mail.gmail.com.
> 
> 

_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to