Closed
Bug 942299
Opened 12 years ago
Closed 11 years ago
Disable Mac OS X 10.7 testing automation and repurpose it as 10.6
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: armenzg)
References
Details
Attachments
(7 files, 1 obsolete file)
|
17.24 KB,
patch
|
bhearsum
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
|
1.42 KB,
patch
|
bhearsum
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
|
81 bytes,
patch
|
bhearsum
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
|
8.88 KB,
text/plain
|
bhearsum
:
review+
armenzg
:
checked-in+
|
Details |
|
2.58 KB,
patch
|
emorley
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
|
909 bytes,
patch
|
coop
:
review+
|
Details | Diff | Splinter Review |
|
1.65 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
I hope to have the 10.7 testing infrastructure disabled by the end of Tuesday.
I will file a Relops bug on Monday/Tuesday with all the details.
Comment 1•12 years ago
|
||
Ccing uberj so he sees the dep bugs as they roll in, too.
| Assignee | ||
Comment 2•11 years ago
|
||
Attachment #8338564 -
Flags: review?
| Assignee | ||
Updated•11 years ago
|
Priority: -- → P2
| Assignee | ||
Updated•11 years ago
|
Attachment #8338564 -
Flags: review? → review?(bhearsum)
Comment 3•11 years ago
|
||
Comment on attachment 8338564 [details] [diff] [review]
remove 10.7 testing across the board
Review of attachment 8338564 [details] [diff] [review]:
-----------------------------------------------------------------
lgtm. Might be good to sanity check with a dump-master or builder_list run.
Attachment #8338564 -
Flags: review?(bhearsum) → review+
| Assignee | ||
Comment 4•11 years ago
|
||
Comment on attachment 8338564 [details] [diff] [review]
remove 10.7 testing across the board
https://hg.mozilla.org/build/buildbot-configs/rev/1f56e6dc01e1
Attachment #8338564 -
Flags: checked-in+
| Assignee | ||
Comment 5•11 years ago
|
||
Attachment #8338744 -
Flags: review?(bhearsum)
| Assignee | ||
Comment 6•11 years ago
|
||
Attachment #8338753 -
Flags: review?(bhearsum)
| Assignee | ||
Comment 7•11 years ago
|
||
This should be included with something like this:
/data/releng/www/slavealloc/slavealloc dbimport -D <db url including password> --slave-data <the csv file you just created containing slaves>
Attachment #8338765 -
Flags: review?(bhearsum)
| Assignee | ||
Comment 8•11 years ago
|
||
Attachment #8338768 -
Flags: review?(emorley)
| Assignee | ||
Comment 9•11 years ago
|
||
Attachment #8338775 -
Flags: review?(coop)
Updated•11 years ago
|
Attachment #8338768 -
Flags: review?(emorley) → review+
Comment 10•11 years ago
|
||
Comment on attachment 8338775 [details] [diff] [review]
remove 10.7 from buildfaster report
Review of attachment 8338775 [details] [diff] [review]:
-----------------------------------------------------------------
We may want to wait a day or two before landing this so that 10.7 test jobs from today get parsed correctly.
Attachment #8338775 -
Flags: review?(coop) → review+
Comment 11•11 years ago
|
||
Comment on attachment 8338753 [details] [diff] [review]
remove talos-r4-lion machines from slavealloc
This DB is case sensitive for table names, it seems. The where clause is fine but make sure you adjust the table name before you run it:
mysql> select name FROM SLAVES WHERE NAME LIKE 'talos-r4-lion-%';
ERROR 1146 (42S02): Table 'buildslaves.SLAVES' doesn't exist
mysql> select name FROM slaves WHERE NAME LIKE 'talos-r4-lion-%';
+-------------------+
| name |
+-------------------+
| talos-r4-lion-001 |
Attachment #8338753 -
Flags: review?(bhearsum) → review+
Comment 12•11 years ago
|
||
Comment on attachment 8338744 [details] [diff] [review]
add the 10.7 machines as 10.6 machines
Per IRC, this should only go up to 173. r=me with that changed.
Attachment #8338744 -
Flags: review?(bhearsum) → review+
Comment 13•11 years ago
|
||
Comment on attachment 8338765 [details]
add 10.6 machines to slavealloc
Per IRC, this should only go up to 173. r=me with that changed.
Attachment #8338765 -
Flags: review?(bhearsum) → review+
| Assignee | ||
Comment 14•11 years ago
|
||
Comment on attachment 8338744 [details] [diff] [review]
add the 10.7 machines as 10.6 machines
Landed as:
- 'snowleopard': dict([("talos-r4-snow-%03i" % x, {}) for x in range(1,85) \
+ 'snowleopard': dict([("talos-r4-snow-%03i" % x, {}) for x in range(1,174) \
Attachment #8338744 -
Flags: checked-in+
| Assignee | ||
Updated•11 years ago
|
Attachment #8338768 -
Flags: checked-in+
| Assignee | ||
Comment 15•11 years ago
|
||
Comment on attachment 8338753 [details] [diff] [review]
remove talos-r4-lion machines from slavealloc
Deployed.
mysql> DELETE FROM slaves WHERE NAME LIKE 'talos-r4-lion-%';
Query OK, 89 rows affected (0.02 sec)
| Assignee | ||
Comment 16•11 years ago
|
||
Here are the values that are used:
mysql> select * from machines where name like 'talos-r4-snow-%' limit 1;
+------+-------+---------------+-----------+-------------------+-----------+------------+
| id | os_id | is_throttling | cpu_speed | name | is_active | date_added |
+------+-------+---------------+-----------+-------------------+-----------+------------+
| 1455 | 21 | 0 | 2.4 | talos-r4-snow-001 | 1 | 1317830270 |
+------+-------+---------------+-----------+-------------------+-----------+------------+
1 row in set (0.00 sec)
Attachment #8339311 -
Flags: review?(bhearsum)
Updated•11 years ago
|
Attachment #8339311 -
Flags: review?(bhearsum) → review+
| Assignee | ||
Updated•11 years ago
|
Attachment #8338753 -
Flags: checked-in+
| Assignee | ||
Comment 17•11 years ago
|
||
Comment on attachment 8338765 [details]
add 10.6 machines to slavealloc
Deployed without 174 and 175.
Attachment #8338765 -
Flags: checked-in+
| Assignee | ||
Comment 18•11 years ago
|
||
Comment on attachment 8339311 [details] [diff] [review]
add the 10.6 machines to the graph server
Too my surprise, somebody had already these entries in 2011 (10/05/11 @ 3:57:50pm UTC) up to machine 183.
Both staging and production graphs are up-to-date.
Attachment #8339311 -
Attachment is obsolete: true
| Assignee | ||
Comment 19•11 years ago
|
||
I've marked all slaves to be added to my staging master:
update slaves set enabled=1, envid=3, poolid=16, locked_masterid=133 where enabled=0 and notes is NULL and name like 'talos-r4-snow-%';
mysql> select count(*) from slaves where locked_masterid=133 and name like 'talos-r4-snow-%';
+----------+
| count(*) |
+----------+
| 89 |
+----------+
1 row in set (0.00 sec)
Comment 20•11 years ago
|
||
in production
| Assignee | ||
Comment 21•11 years ago
|
||
I added all of the slaves that have had green runs.
I've left the following on staging:
* talos-r4-snow-130 - running red on staging
* talos-r4-snow-102 - ping down; I triggered a slaveapi reboot
* talos-r4-snow-103 - ping down; I triggered a slaveapi reboot
* talos-r4-snow-104 - ping down; I triggered a slaveapi reboot
* talos-r4-snow-144 - it is odd; the ping does not timeout; slaveapi reboot takes long to respond
* talos-r4-snow-166 - I can ping it but I can't ssh; slaveapi reboot
* talos-r4-snow-170 - it has not taken a job; uptime 13hours; sudo reboot
| Assignee | ||
Comment 22•11 years ago
|
||
Attachment #8340018 -
Flags: review?(bhearsum)
Updated•11 years ago
|
Attachment #8340018 -
Flags: review?(bhearsum) → review+
Comment 23•11 years ago
|
||
The 10.7 machines were the only machines that allowed me to test apps installations/updates (because on 10.6 and 10.8 machines we don't have enough privileges to write to /Applications).
Could you prioritize bug 942445 now that 10.7 machines are gone?
| Assignee | ||
Comment 24•11 years ago
|
||
(In reply to Marco Castelluccio [:marco] from comment #23)
> The 10.7 machines were the only machines that allowed me to test apps
> installations/updates (because on 10.6 and 10.8 machines we don't have
> enough privileges to write to /Applications).
> Could you prioritize bug 942445 now that 10.7 machines are gone?
Let me follow up on it.
| Assignee | ||
Comment 25•11 years ago
|
||
Machines put in production:
* talos-r4-snow-102
* talos-r4-snow-104
* talos-r4-snow-130
Machines left behind:
* talos-r4-snow-103
* talos-r4-snow-166
* talos-r4-snow-170
Being dealt with on problem tracking bugs:
* talos-r4-snow-144
| Assignee | ||
Comment 26•11 years ago
|
||
| Assignee | ||
Comment 27•11 years ago
|
||
coop, I'm not going to land this.
I believe it has value to leave it around in case someone wants to look at historic data in gofaster.
WFY?
(In reply to Chris Cooper [:coop] from comment #10)
> Comment on attachment 8338775 [details] [diff] [review]
> remove 10.7 from buildfaster report
>
> Review of attachment 8338775 [details] [diff] [review]:
> -----------------------------------------------------------------
>
> We may want to wait a day or two before landing this so that 10.7 test jobs
> from today get parsed correctly.
Flags: needinfo?(coop)
Comment 28•11 years ago
|
||
something here is in production
| Assignee | ||
Comment 29•11 years ago
|
||
coop, if you disagree with what I say please let me know and re-open the bug.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 30•11 years ago
|
||
(In reply to Armen Zambrano [:armenzg] (Release Engineering) (EDT/UTC-4) from comment #27)
> coop, I'm not going to land this.
> I believe it has value to leave it around in case someone wants to look at
> historic data in gofaster.
>
> WFY?
Sure.
Flags: needinfo?(coop)
Updated•7 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•