Filtering MutationObserver polyfill messages from test_controller logging

Filtering MutationObserver polyfill  messages from test_controller logging

Basically the MutationObserver polyfill is using postMessage as a scheduling mechanism when MutationObserver is not supported (IE9,IE10). These messages are getting picked up by the test controller's logging, which is then putting them into the body. This in turn generates new mutation events, generating new messages. Endless loop.

This just filters messages which are random numbers.

BUG=
R=jmesserly@google.com

Committed: https://code.google.com/p/dart/source/detail?r=29107

[blois, 2013-10-23 18:08:18]

For reference, the event is fired from:
https://code.google.com/p/dart/source/browse/branches/bleeding_edge/dart/pkg/...

[Jennifer Messerly, 2013-10-23 18:14:31]

lgtm

https://codereview.chromium.org/34363005/diff/1/pkg/unittest/lib/test_control...
File pkg/unittest/lib/test_controller.js (right):

https://codereview.chromium.org/34363005/diff/1/pkg/unittest/lib/test_control...
pkg/unittest/lib/test_controller.js:101: if (typeof msg != 'string') return;
maybe just move up this check instead?

[blois, 2013-10-23 18:20:22]

https://codereview.chromium.org/34363005/diff/1/pkg/unittest/lib/test_control...
File pkg/unittest/lib/test_controller.js (right):

https://codereview.chromium.org/34363005/diff/1/pkg/unittest/lib/test_control...
pkg/unittest/lib/test_controller.js:101: if (typeof msg != 'string') return;
On 2013/10/23 18:14:32, John Messerly wrote:
> maybe just move up this check instead?

Done, removed try/catch.

[blois, 2013-10-23 18:40:13]

Committed patchset #2 manually as r29107 (presubmit successful).