Aki Sasaki (not active) Reporter
	Description • 14 years ago

Currently we're only testing m-c and tm.

We saw a build system branch merge kill Android startup.
If we had stable tegra tests tracking that branch, they would have been able to see the bustage on their branch.

	Aki Sasaki (not active) Reporter
	Comment 1 • 14 years ago

(Mobile developers are asking for tree closure when things like this happen, which bumps stability and coverage' priority even more than it already has been.)

	Shawn Wilsher :sdwilsh
	Comment 4 • 14 years ago

Places branch also needs coverage.

	Aki Sasaki (not active) Reporter
	Comment 5 • 14 years ago

Patch incoming for try, places, cedar with the talos suites from bug 648800 comment 6 .

Afterwards I'll keep this bug open to enable unittests, other branches, other talos suites.

	Lukas Blakk [:lsblakk] use ?needinfo Assignee
	Comment 7 • 14 years ago

Comment on attachment 525108 [details] [diff] [review]
try,cedar,places talos suites

i'll go take a look at try_parser and update trychooser accordingly if needed

	Aki Sasaki (not active) Reporter
	Comment 8 • 14 years ago

Comment on attachment 525108 [details] [diff] [review]
try,cedar,places talos suites

http://hg.mozilla.org/build/buildbot-configs/rev/97c9140d9c8c

	(no longer active)
	Comment 9 • 14 years ago

FWIW, when I give up using the cedar twig, this change will affect the next person who happens to pick up cedar (as opposed to birch or maple for example).

	Aki Sasaki (not active) Reporter
	Comment 10 • 14 years ago

That's correct.

I'm enabling cedar, try, and places as those are the ones requiring immediate attention.  The plan is to enable all tests everywhere needed, as long as we have enough tegras as to not starve coverage.

I can disable cedar if/when it's no longer needed... when will that be?

	(no longer active)
	Comment 11 • 14 years ago

(In reply to comment #10)
> That's correct.
> 
> I'm enabling cedar, try, and places as those are the ones requiring immediate
> attention.  The plan is to enable all tests everywhere needed, as long as we
> have enough tegras as to not starve coverage.

OK.

> I can disable cedar if/when it's no longer needed... when will that be?

Not clear yet.  I'll try to ping releng when I decide to abandon it.

	Aki Sasaki (not active) Reporter
	Comment 12 • 14 years ago

Aurora and Beta need coverage.

	Aki Sasaki (not active) Reporter
	Comment 13 • 14 years ago

(In reply to comment #12)
> Aurora and Beta need coverage.

Lukas fixed Aurora in bug 648066.

	John O'Duinn [:joduinn] (please use "needinfo?" flag)
	Comment 14 • 13 years ago

(In reply to comment #11)
> (In reply to comment #10)
...
> > I can disable cedar if/when it's no longer needed... when will that be?
> Not clear yet.  I'll try to ping releng when I decide to abandon it.

Ehsan, you still doing cedar? I saw chatter in newsgroups about you stopping using it for landing other people's patches, but I note you still have it in the bookings page.

	Lukas Blakk [:lsblakk] use ?needinfo Assignee
	Comment 16 • 13 years ago

put the tracemonkey v8 suite back in

	Lukas Blakk [:lsblakk] use ?needinfo Assignee
	Comment 17 • 13 years ago

Currently the remote-t* suites are enabled on:

mozilla-central
mozilla-beta
mozilla-aurora
mozilla-2.1
places
try
cedar

So we need to establish if the tegra pool can handle having this on by default in the project_branches loop (see attached patch) and then deploy that if we can support that load.

	Aki Sasaki (not active) Reporter
	Comment 20 • 13 years ago

Comment on attachment 529872 [details] [diff] [review]
enable tegra talos runs on all project_branches -real-real-real

If/when we want to turn tegra talos on for all branches, this looks good.

	Aki Sasaki (not active) Reporter
	Comment 21 • 13 years ago

Philor's asking for tegra unit tests on tracemonkey.

	Aki Sasaki (not active) Reporter
	Comment 22 • 13 years ago

Comment on attachment 536509 [details] [diff] [review]
enable tracemonkey tegra unit tests

http://hg.mozilla.org/build/buildbot-configs/rev/3b22c458b3eb

	Aki Sasaki (not active) Reporter
	Comment 23 • 13 years ago

Bug 663201 is probably more useful than this open-ended bug: it's a specific request with a specific deliverable.

Resolving this; added a patch for mozilla-inbound; we can add more test coverage when requested.