Fix issue with async callbacks that get called synchronously while running test case function causi…

pkg/scheduled_test/lib/scheduled_test.dart

 // Copyright (c) 2013, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 // TODO(nweiz): Add support for calling [schedule] while the schedule is already
 // running.
 // TODO(nweiz): Port the non-Pub-specific scheduled test libraries from Pub.
 /// A package for writing readable tests of asynchronous behavior.
 ///
 /// This package works by building up a queue of asynchronous tasks called a
@@ skipping 298 matching lines @@
 
   unittest.tearDown(() {
     _currentSchedule = null;
   });
 }
 
 /// Ensures that the global configuration for `scheduled_test` has been
 /// initialized.
 void _ensureInitialized() {
   unittest.ensureInitialized();
-  unittest.wrapAsync = (f) {
+  unittest.wrapAsync = (f, [id = '']) {
     if (currentSchedule == null) {
       throw new StateError("Unexpected call to wrapAsync with no current "
           "schedule.");
     }
 
     return currentSchedule.wrapAsync(f);
   };
 }
 
 /// Like [wrapAsync], this ensures that the current task queue waits for
 /// out-of-band asynchronous code, and that errors raised in that code are
 /// handled correctly. However, [wrapFuture] wraps a [Future] chain rather than
 /// a single callback.
 ///
 /// The returned [Future] completes to the same value or error as [future].
 Future wrapFuture(Future future) {
   if (currentSchedule == null) {
     throw new StateError("Unexpected call to wrapFuture with no current "
         "schedule.");
   }
 
   return currentSchedule.wrapFuture(future);
 }