Closed
Bug 1207071
Opened 9 years ago
Closed 8 years ago
remove plugins references in talos
Categories
(Testing :: Talos, defect)
Testing
Talos
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: parkouss, Unassigned)
References
Details
Attachments
(3 files)
40 bytes,
text/x-review-board-request
|
jmaher
:
review+
|
Details |
5.30 KB,
patch
|
Callek
:
review+
|
Details | Diff | Splinter Review |
1.02 KB,
patch
|
Callek
:
review+
|
Details | Diff | Splinter Review |
So, looking at bug 1206415 comment 4, the plugins are obsolete and we should remove them. So I think there are two files that we should change: - testing/mozharness/mozharness/mozilla/testing/talos.py - testing/talos/talos.json
Reporter | ||
Comment 1•9 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=fb4982ddd8eb
Reporter | ||
Comment 2•9 years ago
|
||
Bug 1207071 - remove plugins references in talos. r=jmaher
Attachment #8665518 -
Flags: review?(jmaher)
Comment 3•9 years ago
|
||
Comment on attachment 8665518 [details] MozReview Request: Bug 1207071 - remove plugins references in talos. r=jmaher https://reviewboard.mozilla.org/r/20247/#review18229 this is great! cleanup is awesome to see.
Attachment #8665518 -
Flags: review?(jmaher) → review+
Reporter | ||
Comment 4•9 years ago
|
||
So, I am unable to remove the "--system-bits" option that is used on try (and it was only useful for plugins;): https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/testing/talos.py#103 If I remove that, builds are broken. This is because it appears in the the log, so the thing that call the talos mozharness stuff define that somewhere, and we can't remove option definitions from the talos.py file until we removed that from that *thing*. I found something that may be that thing, in build-central: https://dxr.mozilla.org/build-central/source/buildbotcustom/misc.py#2420 :armenzg, can you help me here so I can remove the option definitions from the talos.py mozharness file (note that there are multiple options that we don't use in there (first link)) ? Am I on the right track, and what should I do to make changes here if it is the case ?
Reporter | ||
Comment 5•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/c2ad005811c5ec45704250cfb90e003426701541 Bug 1207071 - remove plugins references in talos. r=jmaher
Reporter | ||
Comment 6•9 years ago
|
||
leave-open until we know what we do for the option definitions.
Keywords: leave-open
Reporter | ||
Comment 8•9 years ago
|
||
:armenzg, could you look at comment 4 please ? I forgot to NI you. :)
Flags: needinfo?(armenzg)
Comment 9•9 years ago
|
||
What happens if we call talos on a release repo without --system-bits? Is it a mandatory option? If we can call talos on release branches without --system-bits and we don't fail then we're OK to remove that line from misc.py (since it affects talos jobs across the board). If this is not the case, I suggest turning --system-bits an optional parameter and uplift before the buildbotcustom change. Does this help?
Flags: needinfo?(armenzg)
Reporter | ||
Comment 10•9 years ago
|
||
Oh, yep, I am starting to understand thanks! So, should I look into each branch in https://hg.mozilla.org/releases ?
Comment 11•9 years ago
|
||
we only run talos on : try mozilla-beta mozilla-aurora mozilla-central mozilla-inbound fx-team <related trunk based twigs>
Comment 12•9 years ago
|
||
I wanted to see if we have anything left to do here. It sounds like there is some cleanup we can do at the mozharness level. :parkouss, feel free to cl hime in, otherwise, I will look into this early next week.
Flags: needinfo?(jmaher)
Comment 13•9 years ago
|
||
it seems as though we could remove this from buildbot-custom, then once that is deployed, we can clean up the mozharness system-bits.
Flags: needinfo?(jmaher)
Comment 14•9 years ago
|
||
lets see if this works as it is deployed!
Attachment #8701181 -
Flags: review?(bugspam.Callek)
Comment 15•9 years ago
|
||
Comment on attachment 8701181 [details] [diff] [review] byebye_systembits.patch Review of attachment 8701181 [details] [diff] [review]: ----------------------------------------------------------------- I'm assuming that on no tree still active we *require* that bit in the config. If that is true then we'll be fine this way.
Attachment #8701181 -
Flags: review?(bugspam.Callek) → review+
Comment 16•9 years ago
|
||
thanks Callek: https://hg.mozilla.org/build/buildbot-configs/rev/23c34b6f0538
Comment 17•9 years ago
|
||
we need to fix buildbotcustom repo first, then do the buildbot-configs repo. This passes |tox| locally.
Attachment #8701512 -
Flags: review?(bugspam.Callek)
Comment 18•8 years ago
|
||
Comment on attachment 8701512 [details] [diff] [review] bbcustom_nosystembits.patch Review of attachment 8701512 [details] [diff] [review]: ----------------------------------------------------------------- From code inspection, I see no reason that this would fail from a buildbot perspective.
Attachment #8701512 -
Flags: review?(bugspam.Callek) → review+
Comment 20•8 years ago
|
||
In production: https://hg.mozilla.org/build/buildbotcustom/rev/6104875a4a3a
Comment 21•8 years ago
|
||
and the buildbot-configs patch again: https://hg.mozilla.org/build/buildbot-configs/rev/6f21a76b0df7
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment 22•6 years ago
|
||
Removing leave-open keyword from resolved bugs, per :sylvestre.
Keywords: leave-open
You need to log in
before you can comment on or make changes to this bug.
Description
•