Closed
Bug 746427
Opened 13 years ago
Closed 13 years ago
Please insert the following SeaMonkey graphs changes into the graphserver and staging-graphserver
Categories
(Data & BI Services Team :: DB: MySQL, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ewong, Assigned: scabral)
References
Details
insert into branches values (NULL,"SeaMonkey-Release-Non-PGO");
insert into machines values (NULL,6,0,NULL,"Linux_comm-release",1,unix_timestamp());
insert into machines values (NULL,6,0,NULL,"Linux_comm-release_leak_test",1,unix_timestamp());
insert into machines values (NULL,7,0,NULL,"OS_X_10.5_comm-release",1,unix_timestamp());
insert into machines values (NULL,7,0,NULL,"OS_X_10.5_comm-release_leak_test",1,unix_timestamp());
insert into machines values (NULL,8,0,NULL,"WINNT_5.2_comm-release",1,unix_timestamp());
insert into machines values (NULL,8,0,NULL,"WINNT_5.2_comm-release_leak_test",1,unix_timestamp());
insert into machines values (NULL,17,0,NULL,"OS_X_10.6_comm-release",1,unix_timestamp());
insert into machines values (NULL,17,0,NULL,"OS_X_10.6_comm-release_leak_test",1,unix_timestamp());
insert into machines values (NULL,18,0,NULL,"Linux_x86-64_comm-release",1,unix_timestamp());
insert into machines values (NULL,18,0,NULL,"Linux_x86-64_comm-release_leak_test",1,unix_timestamp());
|
Reporter | |
Updated•13 years ago
|
Assignee: server-ops-database → server-ops
Component: Server Operations: Database → Server Operations
QA Contact: cshields → phong
|
||
Comment 1•13 years ago
|
||
Don't you want to do the 3 Linux renames too?
Summary: Please insert please insert the following SeaMonkey graphs changes to into the graphserver and staging-graphserver → Please insert the following SeaMonkey graphs changes into the graphserver and staging-graphserver
|
||
Comment 2•13 years ago
|
||
(In reply to Serge Gautherie (:sgautherie) from comment #1)
> Don't you want to do the 3 Linux renames too?
No those are already correct in the live graphserver, and was a mistake [typo] in the commit to the data in hg
|
|
||
Updated•13 years ago
|
Assignee: server-ops → server-ops-database
Component: Server Operations → Server Operations: Database
QA Contact: phong → cshields
|
|
Assignee | |
Updated•13 years ago
|
Assignee: server-ops-database → scabral
|
|
Assignee | |
Comment 3•13 years ago
|
||
Done on stage and production. There were some values already inserted on both:
mysql> insert into branches values (NULL,"SeaMonkey-Release-Non-PGO");
Query OK, 1 row affected (0.00 sec)
mysql> insert into machines values (NULL,6,0,NULL,"Linux_comm-release",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'Linux_comm-release' for key 2
mysql> insert into machines values (NULL,6,0,NULL,"Linux_comm-release_leak_test",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'Linux_comm-release_leak_test' for key 2
mysql> insert into machines values (NULL,7,0,NULL,"OS_X_10.5_comm-release",1,unix_timestamp());
Query OK, 1 row affected (0.01 sec)
mysql> insert into machines values (NULL,7,0,NULL,"OS_X_10.5_comm-release_leak_test",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)
mysql> insert into machines values (NULL,8,0,NULL,"WINNT_5.2_comm-release",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'WINNT_5.2_comm-release' for key 2
mysql> insert into machines values (NULL,8,0,NULL,"WINNT_5.2_comm-release_leak_test",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'WINNT_5.2_comm-release_leak_test' for key 2
mysql> insert into machines values (NULL,17,0,NULL,"OS_X_10.6_comm-release",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)
mysql> insert into machines values (NULL,17,0,NULL,"OS_X_10.6_comm-release_leak_test",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)
mysql> insert into machines values (NULL,18,0,NULL,"Linux_x86-64_comm-release",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'Linux_x86-64_comm-release' for key 2
mysql> insert into machines values (NULL,18,0,NULL,"Linux_x86-64_comm-release_leak_test",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'Linux_x86-64_comm-release_leak_test' for key 2
mysql>
mysql> insert into branches values (NULL,"SeaMonkey-Release-Non-PGO");
Query OK, 1 row affected (0.00 sec)
mysql> insert into machines values (NULL,6,0,NULL,"Linux_comm-release",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'Linux_comm-release' for key 'name'
mysql> insert into machines values (NULL,6,0,NULL,"Linux_comm-release_leak_test",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'Linux_comm-release_leak_test' for key 'name'
mysql> insert into machines values (NULL,7,0,NULL,"OS_X_10.5_comm-release",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)
mysql> insert into machines values (NULL,7,0,NULL,"OS_X_10.5_comm-release_leak_test",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)
mysql> insert into machines values (NULL,8,0,NULL,"WINNT_5.2_comm-release",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'WINNT_5.2_comm-release' for key 'name'
mysql> insert into machines values (NULL,8,0,NULL,"WINNT_5.2_comm-release_leak_test",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'WINNT_5.2_comm-release_leak_test' for key 'name'
mysql> insert into machines values (NULL,17,0,NULL,"OS_X_10.6_comm-release",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)
mysql> insert into machines values (NULL,17,0,NULL,"OS_X_10.6_comm-release_leak_test",1,unix_timestamp());
Query OK, 1 row affected (0.00 sec)
mysql> insert into machines values (NULL,18,0,NULL,"Linux_x86-64_comm-release",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'Linux_x86-64_comm-release' for key 'name'
mysql> insert into machines values (NULL,18,0,NULL,"Linux_x86-64_comm-release_leak_test",1,unix_timestamp());
ERROR 1062 (23000): Duplicate entry 'Linux_x86-64_comm-release_leak_test' for key 'name'
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
|
||
Updated•11 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
•