EngineeringProductivity/Meetings/2011-12-19: Difference between revisions

Line 101: Line 101:
* Rebooted brasstacks to see if that would magically fix the [https://bugzilla.mozilla.org/show_bug.cgi?id=710449 awful latency] when accessing the ES database.  It didn't, and a number of things failed to restart gracefully; mcote wrote up a [https://intranet.mozilla.org/Auto-tools/brasstacksEnv/Incident20111213 summary] (Intranet link) of what went wrong.
* Rebooted brasstacks to see if that would magically fix the [https://bugzilla.mozilla.org/show_bug.cgi?id=710449 awful latency] when accessing the ES database.  It didn't, and a number of things failed to restart gracefully; mcote wrote up a [https://intranet.mozilla.org/Auto-tools/brasstacksEnv/Incident20111213 summary] (Intranet link) of what went wrong.
** In the end, IT fixed the routing problem themselves.  Access had only been granted to one of the three addresses that the ES server's hostname resolved to, resulting in a connection timeout 2/3 of the time.
** In the end, IT fixed the routing problem themselves.  Access had only been granted to one of the three addresses that the ES server's hostname resolved to, resulting in a connection timeout 2/3 of the time.
* mcote starting the [[auto-tools/AutoTestingGuide|Automatic Testing Guide]], a very short summary of all our frameworks along with a Q & A (or flowchart?) to help people decide what framework to use when they want to add a test.
** We *need* to keep this up to date. mcote recommends that, every two weeks, the meeting MC goes over the guide to make sure it's not full of lies.


* Goals Time again
* Goals Time again
Confirmed users
1,927

edits