Closed Bug 509282 Opened 15 years ago Closed 15 years ago

Run Tp4 (and all other tests?) on Talos Try

Categories

(Release Engineering :: General, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: catlee, Assigned: anodelman)

References

Details

Attachments

(1 file)

We should be running Tp4 on Talos Try.  Do we need to be running all the same tests as we do on production try?  I would think we should, unless there's a good reason not to.
Alice: As you just got TP4 running on m-c and the various project branches, can you have a look at this too?

Its seems reasonable (even required?) for developers to be able to run the same suites in try Talos as we run on production Talos, imho.
Assignee: nobody → anodelman
Blocks: 473821
This will add all the missing tests except for nochrome.  I think that nochrome would mostly end up being a timewaster on try, and we have a limited number of slaves there.

During roll out we need to remember to provide the talos try master with a plugins.zip/pageset.zip.
Attachment #393976 - Flags: review?(bhearsum)
Comment on attachment 393976 [details] [diff] [review]
add jss/tp4/other missing tests to talos try

Looks good to me.
Attachment #393976 - Flags: review?(bhearsum) → review+
Comment on attachment 393976 [details] [diff] [review]
add jss/tp4/other missing tests to talos try

changeset:   1429:12841e297af5
Attachment #393976 - Flags: checked-in+
Since this was just a reconfig with no effect on currently up machines I pushed the change tonight.
Rolled out and green.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: