Closed Bug 1340716 Opened 6 years ago Closed 5 years ago

Determine proper steps to avoid Windows test hosts reboots after TCW

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: hwine, Unassigned)

References

()

Details

After we reopened trees from the Feb 11 TCW, philor reported some issues due to slavealloc being shutdown during the TCW.

What are the proper steps to either:
 a) avoid the problem in advance of the TCW, or
 b) easily perform the needed reboots afterwards?

More details, and some ideas, are in https://github.com/mozilla-releng/TCW-history/issues/18 which I'm closing.

All future work on finding a solution will occur in this bug
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.