Description
There are two tests failing in the optimized dart_client buildbot.
Path: client/samples/dartcombat/dartcombat_tests
--- stdout ---
Content-Type: text/plain
Running /mnt/data/b/build/slave/dart_client-linux-chromium-release/build/dart/client/tests/client/samples/dartcombat/dartcombat_tests.dart
Player 1 board:
Known of enemy's board:
ENEMY IS NOT READY0 <= 0 (0 + 0); 0
Player 2 board:
Known of enemy's board:
ENEMY IS NOT READY0 <= 0 (0 + 0); 0
EOF
CONSOLE MESSAGE: line 262: Uncaught TypeError: Cannot read property 'count' of undefined
Command: /mnt/data/b/build/slave/dart_client-linux-chromium-release/build/dart/client/tests/drt/DumpRenderTree --no-timeout "--dart-flags=--enable_asserts --enable_type_checks --ignore-unrecognized-flags" /mnt/data/b/build/slave/dart_client-linux-chromium-release/build/dart/client/out/Release_ia32/client_tests_client_samples_dartcombat_dartcombat_tests.dart.html
=== releaseia32 chromium client/samples/swarm/swarm_tests ===
Path: client/samples/swarm/swarm_tests
--- stdout ---
Content-Type: text/plain
Running /mnt/data/b/build/slave/dart_client-linux-chromium-release/build/dart/client/tests/client/samples/swarm/swarm_tests.dart
Swarm
Section 1
Section 2
Section 3
EOF
CONSOLE MESSAGE: line 560: Uncaught TypeError: Cannot read property 'count' of undefined
Command: /mnt/data/b/build/slave/dart_client-linux-chromium-release/build/dart/client/tests/drt/DumpRenderTree --no-timeout "--dart-flags=--enable_asserts --enable_type_checks --ignore-unrecognized-flags" /mnt/data/b/build/slave/dart_client-linux-chromium-release/build/dart/client/out/Release_ia32/client_tests_client_samples_swarm_swarm_tests.dart.html
===
=== 2 tests failed
An initial scan through buildbot logs shows the dart_combat failure happening intermittently at least as far back as r1624 (I can't definitively say that it wasn't happening before 1624). The failure in the test was intermittent, and became solidly red in the past few days.
The earliest build I see the swarm test failures is r1792.
When I run with --disable-type-optimizations, the failure doesn't reproduce for me (and the non-optimized buildbot has been green the whole time).