Closed Bug 617733 Opened 15 years ago Closed 15 years ago

Add linux qt entries to graphserver

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jhford, Assigned: jhford)

References

Details

Attachments

(1 file)

Attached patch graphs-v1Splinter Review
To make leak/bloat logs easier The attached patch adds a second set of machines to the Centos 5 OS list. I dont know if that is the best way to do this or whether I should create a new OS. If this patch is ok, can you please run the following sql on the staging graph server? insert into machines values (NULL,6,0,NULL,"Linux_QT_mozilla-1.9.1",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_mozilla-1.9.1_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_mozilla-central",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_mozilla-central_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_mozilla-2.0",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_mozilla-2.0_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_tracemonkey",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_tracemonkey_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_places",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_places_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_electrolysis",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_electrolysis_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_lorentz",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_lorentz_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_tryserver",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_tryserver_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_maple",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_maple_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_cedar",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_cedar_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_birch",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_birch_leak_test",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_jaegermonkey",1,unix_timestamp()); insert into machines values (NULL,6,0,NULL,"Linux_QT_jaegermonkey_leak_test",1,unix_timestamp());
Attachment #496270 - Flags: review?(anodelman)
Assignee: nobody → jhford
Attachment #496270 - Flags: review?(anodelman) → review+
On graphs-stage: mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_mozilla-1.9.1",1,unix_timestamp()); Query OK, 1 row affected (0.02 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_mozilla-1.9.1_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_mozilla-central",1,unix_timestamp()); Query OK, 1 row affected (0.02 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_mozilla-central_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.02 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_mozilla-2.0",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_mozilla-2.0_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_tracemonkey",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_tracemonkey_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_places",1,unix_timestamp()); Query OK, 1 row affected (0.01 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_places_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_electrolysis",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_electrolysis_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_lorentz",1,unix_timestamp()); Query OK, 1 row affected (0.01 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_lorentz_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_tryserver",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_tryserver_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.01 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_maple",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_maple_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_cedar",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_cedar_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.01 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_birch",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_birch_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.00 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_jaegermonkey",1,unix_timestamp()); Query OK, 1 row affected (0.02 sec) mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_jaegermonkey_leak_test",1,unix_timestamp()); Query OK, 1 row affected (0.01 sec)
Hmm, still not adding staging results to graph server Executing: ['python', '/builds/slave/mozilla-central-linuxqt/tools/buildfarm/utils/graph_server_post.py', '--server', 'graphs-stage.mozilla.org', '--selector', '/server/collect.cgi', '--branch', 'MozillaTest', '--buildid', '20101209091056', '--sourcestamp', 'e56f745705a8', '--resultsname', 'Linux_QT_mozilla-central', '--properties-file', 'properties.json', '--timestamp', '1291914632'] Process stdio: Process stderr: results not added, response: No machine_name called 'Linux_QT_mozilla-central' can be found File "/var/www/html/graphs2/server/pyfomatic/collect.py", line 260, in handleRequest metadata = MetaDataFromTalos(databaseCursor, databaseModule, inputStream) File "/var/www/html/graphs2/server/pyfomatic/collect.py", line 59, in __init__ self.doDatabaseThings(databaseCursor) File "/var/www/html/graphs2/server/pyfomatic/collect.py", line 88, in doDatabaseThings raise DatabaseException("No machine_name called '%s' can be found" % self.machine_name) Even though mysql> insert into machines values -> (NULL,6,0,NULL,"Linux_QT_mozilla-central",1,unix_timestamp()); Query OK, 1 row affected (0.02 sec)
This is caused by bug 614618, which is being reverted.
Here's a question: what in production is graphs-stage being used for, exactly? We need to work on removing that dependency.
Try results, which would be removed by bug 618060.
Aki: that bug talks about graphs, should it actually make reference to graphs-stage? Just want to be sure I understand.
Possibly, though I don't think it references any specific graph server, just "the graph server". Aiui, with the --screen option we would remove any graph posting whatsoever on Try talos runs. Since Try talos is the only thing in production posting to graphs-stage.m.o, that should solve this problem.
I kinda agree with Laura from a purely IT standpoint. No mixing staging and prod :) How can IT help you get out of this situation?
(In reply to comment #8) > I kinda agree with Laura from a purely IT standpoint. > > No mixing staging and prod :) > > How can IT help you get out of this situation? I dunno, but lets file a new bug for that. My guess is that setting up a second production graph server that is only used for try would be the ticket. Not sure though.
Depends on: 618117
in staging, production and checked into hg
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: