[Sync] Re-re-reland 81454. This time with fixed waitable event usage.

[Sync] Re-re-reland 81454. This time with fixed waitable event usage.

Original codereview: http://codereview.chromium.org/6811003

BUG=77964, 79410
TEST=unit tests

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=82310

[akalin, 2011-04-20 00:18:13]

LGTM

I assume this diff is based off the original CL, but what you'll land is both of
them combined.

http://codereview.chromium.org/6880051/diff/1/chrome/browser/sync/glue/non_fr...
File chrome/browser/sync/glue/non_frontend_data_type_controller_unittest.cc
(right):

http://codereview.chromium.org/6880051/diff/1/chrome/browser/sync/glue/non_fr...
chrome/browser/sync/glue/non_frontend_data_type_controller_unittest.cc:188:
TestTimeouts::action_max_timeout_ms()));
does this have to be action_max_timeout instead of action_timeout?

[Nicolas Zea, 2011-04-20 00:41:55]

Fixed initialization of watiable event, committing once trybots go green.

http://codereview.chromium.org/6880051/diff/1/chrome/browser/sync/glue/non_fr...
File chrome/browser/sync/glue/non_frontend_data_type_controller_unittest.cc
(right):

http://codereview.chromium.org/6880051/diff/1/chrome/browser/sync/glue/non_fr...
chrome/browser/sync/glue/non_frontend_data_type_controller_unittest.cc:188:
TestTimeouts::action_max_timeout_ms()));
On 2011/04/20 00:18:14, akalin wrote:
> does this have to be action_max_timeout instead of action_timeout?

Done.

[commit-bot: I haz the power, 2011-04-20 01:31:06]

Can't apply patch for file
chrome/browser/sync/glue/non_frontend_data_type_controller_unittest.cc.
patching file
chrome/browser/sync/glue/non_frontend_data_type_controller_unittest.cc
Hunk #1 FAILED at 116.
Hunk #2 FAILED at 176.
Hunk #3 FAILED at 207.
3 out of 3 hunks FAILED -- saving rejects to file
chrome/browser/sync/glue/non_frontend_data_type_controller_unittest.cc.rej