Closed
Bug 1232575
Opened 9 years ago
Closed 8 years ago
Distributing the tests on try branch to a separated worker type
Categories
(Firefox Build System :: Task Configuration, task, P3)
Firefox Build System
Task Configuration
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: edgar, Unassigned)
References
Details
(Whiteboard: [EMU] [CI])
+++ This bug was initially created as a clone of Bug #1215766 +++
Per discussion in mozlando work week, we could create a b2gtest-emulator-try worker for the tests running on try branch.
Reporter | ||
Updated•9 years ago
|
Blocks: emu-x86-kk-tests
Reporter | ||
Comment 1•9 years ago
|
||
Hi Greg, could you kindly guide me on how to patch the task graph and also help to create b2gtest-emulator-try? Thank you.
Flags: needinfo?(garndt)
Updated•9 years ago
|
Whiteboard: [EMU] [CI]
Comment 2•9 years ago
|
||
Sorry for the delayed response, this got buried while on holiday and PTO. Now that I'm back I will be clearing these up soon.
I need to experiment with something with our in-tree configuration. It's not initially supported to do this as I originally thought so a few options will need to be tested.
Updated•9 years ago
|
Priority: -- → P3
Updated•9 years ago
|
Assignee: nobody → garndt
Comment 3•9 years ago
|
||
Based on the current status of tests on emulator and hidden jobs, is this still a priority? We have people working on our next versions of in-tree configuration and it might make sense for them to work on it with this in mind rather than trying to patch our current way of doing it.
Flags: needinfo?(garndt)
Updated•9 years ago
|
Assignee: garndt → nobody
Comment 4•9 years ago
|
||
I believe that since most of these jobs either have been disabled or moved to tier 3 this is not as much of a pressing issue. It is something to consider for the in-tree refactoring if it's something we would like to support.
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: TaskCluster → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•