Re: TBPL job visibility policy - now documented

2013-03-26 Thread Steve Fink
On 03/26/2013 07:10 AM, Ed Morley wrote: > (Please reply to dev.tree-management) > > Until now, the requirements for a new platform/test-suite to be shown in > the default TBPL view have been scattered across many newsgroup > discussions, bugs & IRC conversations, which understandably leads to > s

Re: TBPL job visibility policy - now documented

2013-03-26 Thread Ed Morley
I've replied to the last few posts on dev.tree-management :-) https://lists.mozilla.org/listinfo/dev-tree-management https://groups.google.com/d/topic/mozilla.dev.tree-management/N8xmYtgVp74/discussion On 3/26/2013 7:10 AM, Ed Morley wrote: (Please reply to dev.tree-management) __

Re: TBPL job visibility policy - now documented

2013-03-26 Thread Ben Hearsum
On 03/26/13 12:20 PM, Dave Townsend wrote: > On 3/26/2013 9:17 AM, Benjamin Smedberg wrote: >> On 3/26/2013 12:07 PM, Dave Townsend wrote: >>> This is awesome, thanks for writing this up, it's made me spot one >>> more place where Jetpack is failing. >>> >>> Can we get some more definition around "

Re: TBPL job visibility policy - now documented

2013-03-26 Thread Ryan VanderMeulen
On 3/26/2013 12:07 PM, Dave Townsend wrote: This is awesome, thanks for writing this up, it's made me spot one more place where Jetpack is failing. Can we get some more definition around "Runs on all trees that merge into mozilla-central"? In particular I want to make that true for Jetpack but I

Re: TBPL job visibility policy - now documented

2013-03-26 Thread Dave Townsend
On 3/26/2013 9:17 AM, Benjamin Smedberg wrote: On 3/26/2013 12:07 PM, Dave Townsend wrote: This is awesome, thanks for writing this up, it's made me spot one more place where Jetpack is failing. Can we get some more definition around "Runs on all trees that merge into mozilla-central"? In parti

Re: TBPL job visibility policy - now documented

2013-03-26 Thread Ben Hearsum
On 03/26/13 12:17 PM, Benjamin Smedberg wrote: > On 3/26/2013 12:07 PM, Dave Townsend wrote: >> This is awesome, thanks for writing this up, it's made me spot one >> more place where Jetpack is failing. >> >> Can we get some more definition around "Runs on all trees that merge >> into mozilla-centr

Re: TBPL job visibility policy - now documented

2013-03-26 Thread Benjamin Smedberg
On 3/26/2013 12:07 PM, Dave Townsend wrote: This is awesome, thanks for writing this up, it's made me spot one more place where Jetpack is failing. Can we get some more definition around "Runs on all trees that merge into mozilla-central"? In particular I want to make that true for Jetpack bu

Re: TBPL job visibility policy - now documented

2013-03-26 Thread Dave Townsend
This is awesome, thanks for writing this up, it's made me spot one more place where Jetpack is failing. Can we get some more definition around "Runs on all trees that merge into mozilla-central"? In particular I want to make that true for Jetpack but I don't know what all those trees are. Da

Re: TBPL job visibility policy - now documented

2013-03-26 Thread Justin Lebar
> 4) Runs on every push I thought many tests don't run on every push to m-i, due to coalescing. (Just to be clear, I wish we could disable coalescing on m-i!) But also, PGO builds/tests are not run on every push to m-c. -Justin On Tue, Mar 26, 2013 at 10:10 AM, Ed Morley wrote: > (Please repl

TBPL job visibility policy - now documented

2013-03-26 Thread Ed Morley
(Please reply to dev.tree-management) Until now, the requirements for a new platform/test-suite to be shown in the default TBPL view have been scattered across many newsgroup discussions, bugs & IRC conversations, which understandably leads to surprise when developers working on bringing a new