Issue 13524 in dart: pkg/scheduled_test/test/scheduled_server_test fails with MockClock having wrong number of ticks

[da...@googlecode.com]

Status: Triaged
Owner: ----
CC: whe...@google.com
Labels: Type-Defect Priority-Medium Library-ScheduledTest

New issue 13524 by whe...@google.com:
pkg/scheduled_test/test/scheduled_server_test fails with MockClock having
wrong number of ticks
http://code.google.com/p/dart/issues/detail?id=13524

The test sometimes fails with mock_clock having 3 ticks instead of 2. This
does not happen on every run.
Marked as flaky in the status file on all platforms.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[da...@googlecode.com]

Updates:
Labels: Area-Library

Comment #1 on issue 13524 by sand...@google.com:

pkg/scheduled_test/test/scheduled_server_test fails with MockClock having
wrong number of ticks
http://code.google.com/p/dart/issues/detail?id=13524

(No comment was entered for this change.)

[da...@googlecode.com]

Updates:
Labels: -Area-Library Area-Pkg

Comment #2 on issue 13524 by ajoh...@google.com:

pkg/scheduled_test/test/scheduled_server_test fails with MockClock having
wrong number of ticks
http://code.google.com/p/dart/issues/detail?id=13524

Looking at the test, I'm a bit confused to how this mock_clock is actually
mocking a clock. 'timeOfExecution' is not used, and a error-message from
the schedule is expected to contain exactly 2 ms. Does the server know
about schedule?

[da...@googlecode.com]

Updates:
Status: Fixed

Comment #4 on issue 13524 by nw...@google.com:

pkg/scheduled_test/test/scheduled_server_test fails with MockClock having
wrong number of ticks

https://code.google.com/p/dart/issues/detail?id=13524

Fixed by 4b027202ac9e0a4a2bfeef66ffee31e480436b5e