Closed
Bug 835089
Opened 13 years ago
Closed 13 years ago
buildjson/builds-running.js incorrectly listing jobs for mozilla-b2g18_v1_0_0
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: Callek)
References
Details
Attachments
(3 files, 2 obsolete files)
|
194.37 KB,
text/plain
|
Callek
:
feedback+
|
Details |
|
194.37 KB,
text/plain
|
Details | |
|
1.06 KB,
patch
|
nthomas
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
So having triggered a handful of jobs on b2g18_v1_0_0 today, via "Rebuild" I don't see any jobs as pending/running when I look at it. Though it does show me the completed jobs.
I don't know if one of the regex's in here are causing us pain, or if its a releng bug. For the moment, since self-serve shows the stuff fine I'm going to assume TBPL bug.
I'll leave it to John if this is a weekend blocker, but I suspect not.
Comment 1•13 years ago
|
||
Running builds on TBPL are client-side generated using https://secure.pub.build.mozilla.org/builddata/buildjson/builds-running.js
Inspecting that file shows b2g18_v1_0_0 buildernames matched against the b2g18 tree.
-> Releng
(Note: tbpl uses the same regexes for everything, so you'd either get no jobs shown, or all. The only issue that has been known to happen in the past is recent *completed* jobs for all trees not showing, due to TBPL's data import cron getting stuck. However the error handling for that has been recently improved, so even that shouldn't occur from now on. Best bet in the case of TBPL issues is to refer to the json file provided by releng to see whether it's TBPL's fault or a buildbot/releng script issue :-)).
Component: Tinderboxpushlog → Release Engineering: Automation (General)
No longer depends on: 835019
OS: Windows 7 → All
Product: Webtools → mozilla.org
QA Contact: catlee
Hardware: x86_64 → All
Version: Trunk → other
| Assignee | ||
Comment 2•13 years ago
|
||
As far as I can tell this is the code that needs to change...
This should also fix Bug 751066, though I went with this approach in part because of how that bug played out (needing to be backed out).
To help trace callstack this is what I saw:
Running with fmt=json: http://mxr.mozilla.org/build/source/buildapi/buildapi/controllers/running.py
Index of results page: http://mxr.mozilla.org/build/source/buildapi/buildapi/controllers/results.py#25
Getting running builds list: http://mxr.mozilla.org/build/source/buildapi/buildapi/controllers/results.py#46
Figure out branch name based on results from buildbotDB: http://mxr.mozilla.org/build/source/buildapi/buildapi/model/query.py#116
We then see the "mozilla-b2g18" info before we see the "mozilla-b2g18_v1_0_0" and because we do startswith we leave the loop early and say we're "mozilla-b2g18": http://mxr.mozilla.org/build/source/buildapi/buildapi/model/query.py#34
Assignee: nobody → bugspam.Callek
Status: NEW → ASSIGNED
Attachment #706822 -
Flags: review?(nthomas)
| Assignee | ||
Comment 3•13 years ago
|
||
...I wonder what language I coded that in, since .length() is not actually the python syntax. This should do it
Attachment #706822 -
Attachment is obsolete: true
Attachment #706822 -
Flags: review?(nthomas)
Attachment #706824 -
Flags: review?(nthomas)
Comment 4•13 years ago
|
||
Comment on attachment 706824 [details] [diff] [review]
[buildapi] v1.1
This would cause regressions, where sourcestamps with branches like accessibility-linux-talos would be left alone rather than returning accessibility.
Attachment #706824 -
Flags: review?(nthomas) → review-
Comment 5•13 years ago
|
||
See cruncher:~nthomas/bug835089 for how this was generated. 'grep -v OK' for the failures. Mostly talos, some release branch.
Comment 6•13 years ago
|
||
This has the changes you want for mozilla-b2g18_v1_0_0 and try-comm-central. I'm not sure what the story with those release branches is, they may be obsolete now but we'd have to look into it.
This requires this additional patch:
diff --git a/buildapi/model/query.py b/buildapi/model/query.py
--- a/buildapi/model/query.py
+++ b/buildapi/model/query.py
@@ -9,8 +9,9 @@ import math, re, time
def GetAllBranches():
ss = meta.scheduler_db_meta.tables['sourcestamps']
q = select([ss.c.branch]).distinct()
q = q.where(not_(ss.c.branch.like("%unittest")))
+ q = q.where(not_(ss.c.branch.like("%talos")))
results = q.execute()
# exclude defunct branches
exclusions = ('releases/mozilla-1.9.3',
| Assignee | ||
Comment 7•13 years ago
|
||
Comment on attachment 706943 [details]
comparison, using attachment 706824 [details] [diff] [review]
I say we go with it, and look into the releasy stuff, we don't exactly support self serve for release jobs anyway [yet].
Attachment #706943 -
Flags: feedback+
| Assignee | ||
Comment 8•13 years ago
|
||
Do it, and exclude talos
Attachment #706824 -
Attachment is obsolete: true
Attachment #707421 -
Flags: review?(nthomas)
Comment 9•13 years ago
|
||
Comment on attachment 707421 [details] [diff] [review]
[buildapi] v2
http://hg.mozilla.org/build/buildapi/rev/4651e82bc894
Attachment #707421 -
Flags: review?(nthomas)
Attachment #707421 -
Flags: review+
Attachment #707421 -
Flags: checked-in+
Comment 10•13 years ago
|
||
Got autodeployed without issue, and looks good in production.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
No longer blocks: 835865
Summary: TBPL not showing "running" builds for mozilla-b2g18_v1_0_0 → buildjson/builds-running.js incorrectly listing jobs for mozilla-b2g18_v1_0_0
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•