Closed
Bug 653328
Opened 13 years ago
Closed 13 years ago
Create Mozilla-Beta-Release branch in graphs
Categories
(Data & BI Services Team :: DB: MySQL, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: mpressman)
References
Details
Attachments
(1 file)
1014 bytes,
patch
|
nthomas
:
review+
|
Details | Diff | Splinter Review |
already created the tinderbox tree.
Attachment #528774 -
Flags: review?(nrthomas)
Updated•13 years ago
|
Attachment #528774 -
Flags: review?(nrthomas) → review+
Reporter | ||
Updated•13 years ago
|
Attachment #528774 -
Flags: checked-in+
Reporter | ||
Comment 1•13 years ago
|
||
Could you folks please add this new branch to production and staging graph servers? The SQL to run is insert into branches values (NULL,"Mozilla-Beta-Release");
Assignee: catlee → server-ops-releng
Component: Release Engineering → Server Operations: RelEng
Flags: checked-in+
QA Contact: release → zandr
Comment 2•13 years ago
|
||
production is tm-b01-master01:graphs_mozilla_org_new stage is tm-stage01-master01:graphs_stage2
Assignee: server-ops-releng → mpressman
Comment 3•13 years ago
|
||
I'm assuming this is completed since http://hg.mozilla.org/graphs/rev/f2c54c01dfb2 has landed - ready to close?
Assignee | ||
Comment 4•13 years ago
|
||
succeeded
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 5•13 years ago
|
||
When we tried to submit results on the Mozilla-Beta-Release branch we got this error: RETURN:send failed, graph server says: RETURN:No branch_id for a branch_name 'Mozilla-Beta-Release' can be found RETURN: File "/data/www/graphs.mozilla.org/server/pyfomatic/collect.py", line 264, in handleRequest RETURN: metadata = MetaDataFromTalos(databaseCursor, databaseModule, inputStream) RETURN: File "/data/www/graphs.mozilla.org/server/pyfomatic/collect.py", line 59, in __init__ RETURN: self.doDatabaseThings(databaseCursor) RETURN: File "/data/www/graphs.mozilla.org/server/pyfomatic/collect.py", line 109, in doDatabaseThings RETURN: raise DatabaseException("No branch_id for a branch_name '%s' can be found" % self.branch_name) Could you double check the production database ?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 6•13 years ago
|
||
I checked production and it did not contain the value in graphs_mozilla_org_new.branches nor did it contain it in stage so I added them both.
Comment 7•13 years ago
|
||
Thanks. Unfortunately, we hit the same error for more Firefox beta builds on Friday, eg http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Beta-Release/1306519067.1306519332.14873.gz&fulltext=1. If I connect to the production db (based on the access info for catlee's regression detector), then equivalent code appears to work just fine: mysql> select id from branches where name="Mozilla-Beta-Release"; +----+ | id | +----+ | 62 | +----+ 1 row in set (0.00 sec) lsblakk/catlee/rhelmer, any ideas what's happening here ?
Comment 8•13 years ago
|
||
(In reply to comment #7) > Thanks. Unfortunately, we hit the same error for more Firefox beta builds on > Friday, eg > http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Beta-Release/1306519067. > 1306519332.14873.gz&fulltext=1. If I connect to the production db (based on > the access info for catlee's regression detector), then equivalent code > appears to work just fine: > > mysql> select id from branches where name="Mozilla-Beta-Release"; > +----+ > | id | > +----+ > | 62 | > +----+ > 1 row in set (0.00 sec) > > lsblakk/catlee/rhelmer, any ideas what's happening here ? I don't have access to anything in prod, but I tried to repro in staging and works there. Can someone show me the actual results that are being posted? I mocked up this example just to test on stage: [rhelmer@bm-buildgraph01 ~]$ cat test.txt START AVERAGE talos-rev2-xp25, tzoom, Mozilla-Beta-Release, changeset_1, 13, 1229477017 2.0 END [rhelmer@bm-buildgraph01 ~]$ curl -F filename=@test.txt 'http://graphs-stage.mozilla.org/server/collect.cgi' RETURN tzoom 2.00 graph.html#tests=[{"test":60,"branch":55,"machine":358}] Looking at the code linked in the traceback, it would be nice if we were logging the actual exception here, this might be a red herring (although given comment 7 I'd be kind of surprised). If this is still happening and there are no other leads, I suggest we log the actual exception here http://hg.mozilla.org/graphs/file/60e1136a3551/server/pyfomatic/collect.py#l107
Updated•13 years ago
|
Component: Server Operations: RelEng → Server Operations: Database
QA Contact: zandr → mrz
Comment 9•13 years ago
|
||
Appears to be working for the builds today, and for the last couple of betas. Very strange.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Data & BI Services Team
You need to log in
before you can comment on or make changes to this bug.
Description
•