Closed
Bug 1384706
Opened 7 years ago
Closed 7 years ago
trychooser syntax should not invoke buildbot jobs by default
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kmoir, Assigned: kmoir)
References
Details
Attachments
(3 files, 5 obsolete files)
37.09 KB,
patch
|
catlee
:
feedback+
|
Details | Diff | Splinter Review |
33.74 KB,
patch
|
kmoir
:
checked-in+
|
Details | Diff | Splinter Review |
51 bytes,
text/x-github-pull-request
|
Details | Review |
If you run -b do -p all on try, the win buildbot build jobs run as well. However, they shouldn't run now with the tcmigration of win32/win64
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → kmoir
Assignee | ||
Comment 1•7 years ago
|
||
i.e. https://treeherder.mozilla.org/#/jobs?repo=try&revision=44e7c06da9dbf163c790a21b5679aab247a247bc
Assignee | ||
Comment 2•7 years ago
|
||
So would it be okay to change the scheduling for this to remove these extra windows builders on try but leave them on esr and release. Like what we did when removed them for mac. It seems like a cleaner change than changing the try syntax.
Flags: needinfo?(catlee)
Comment 3•7 years ago
|
||
I think we wanted to leave them on try so that people had some way of testing patches for ESR/Release without having to land there. At this point, I'm not sure how much value there is in that. How hard is it to update the Try syntax?
Flags: needinfo?(catlee)
Assignee | ||
Comment 4•7 years ago
|
||
I have some patches in progress to update the try syntax
Assignee | ||
Comment 5•7 years ago
|
||
These are my initial patches but looking at them, I realize I need to take a completely different approach. I need to add flag like like --winlegacy instead of modifying another value like alllegacy to strip out win builds on all and when the platform is specified explicitly. If this flag is enabled, I can allow the filter to pass windows builders, if not then remove them by default. Might need to modify the taskcluster try parser too so it doesn't break with the new syntax as well.
Assignee | ||
Comment 6•7 years ago
|
||
Attachment #8898588 -
Attachment is obsolete: true
Assignee | ||
Comment 7•7 years ago
|
||
I modified the bb side of the trychooser syntax builder to include a new value called --win or -w all to include windows platforms to be run. Without this value, all the windows platforms will be removed from the list of builds that are run. I also fixed existing tests, added new tests and commented out some tests that I don't think are relevant anymore. I looked at the taskcluster trychooser code and I don't think it needs to be modified to accommodate this since all windows jobs should be triggered by tc and the syntax isn't the same anyways.
Attachment #8899572 -
Attachment is obsolete: true
Attachment #8899581 -
Flags: feedback?
Comment 8•7 years ago
|
||
How about a '--buildbot' flag? If it's not set, then treat user_platforms as empty. I think we need support for the old OSX jobs too, not just windows.
Assignee | ||
Comment 9•7 years ago
|
||
Attachment #8899581 -
Attachment is obsolete: true
Attachment #8899581 -
Flags: feedback?
Assignee | ||
Updated•7 years ago
|
Attachment #8899605 -
Flags: feedback?
Comment 10•7 years ago
|
||
Comment on attachment 8899605 [details] [diff] [review] bug1384706-5.patch Review of attachment 8899605 [details] [diff] [review]: ----------------------------------------------------------------- ::: try_parser.py @@ +312,5 @@ > default='none', > dest='talos', > help='provide a list of talos tests, or specify all (default is None)') > + parser.add_argument('--buildbot', > + default='none', Should this be None? Or turn this into a boolean switch - see comments below. @@ +397,2 @@ > else: > user_platforms.add(platform) If my try syntax includes '-p win32', then we would get buildbot jobs due to this line too. What about if '--buildbot' isn't present, then user_platforms is just set(), and we exit? So the try syntax required for windows buildbot jobs would be something like "try: -b do -p win32 --buildbot"
Assignee | ||
Comment 11•7 years ago
|
||
Attachment #8899605 -
Attachment is obsolete: true
Attachment #8899605 -
Flags: feedback?
Assignee | ||
Updated•7 years ago
|
Attachment #8900855 -
Flags: feedback?
Assignee | ||
Comment 12•7 years ago
|
||
Attachment #8900855 -
Attachment is obsolete: true
Attachment #8900855 -
Flags: feedback?
Assignee | ||
Updated•7 years ago
|
Attachment #8902401 -
Flags: feedback?(catlee)
Comment 13•7 years ago
|
||
Comment on attachment 8902401 [details] [diff] [review] bug1384706-8.patch Review of attachment 8902401 [details] [diff] [review]: ----------------------------------------------------------------- looks great, thanks!
Attachment #8902401 -
Flags: feedback?(catlee) → feedback+
Assignee | ||
Comment 15•7 years ago
|
||
patch with commented out tests removed.
Assignee | ||
Comment 16•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Attachment #8903656 -
Flags: checked-in+
Assignee | ||
Comment 17•7 years ago
|
||
verified that the spurious windows jobs aren't running on try, still have to deploy a new version of releng services in bug 1397326 to fix the try chooser syntax
Comment 18•7 years ago
|
||
I think this broke try-comm-central.
Comment 19•7 years ago
|
||
This did break try-comm-central specifying linux/linux64 builds (see Bug 1402808).
Blocks: 1402808
Assignee | ||
Comment 20•7 years ago
|
||
The trychooser deploy happened today so closing.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•