Bob Nystrom
6c757957db
DDC's codegen test copies those files to a local "gen" directory so that it can do stuff like splitting out the multitests before it compiles them to JS. I left all of that alone, so the rest of DDC's test infrastructure is unchanged. The very first step that builds the "gen" directory just copies from sdk/tests/..._strong/... instead and the rest is good to go. I did not move not_yet_strong_tests.dart somewhere more accessible yet because I'm not sure if kernel needs it or where it should go. I did not create any status files because DDC doesn't need them and there are no test suites for the new directories for the other platforms.
31 lines
1011 B
Dart
31 lines
1011 B
Dart
library async_cancellingisolate;
|
|
|
|
import 'dart:async';
|
|
import 'package:unittest/unittest.dart';
|
|
|
|
main(message, replyTo) {
|
|
var command = message.first;
|
|
expect(command, 'START');
|
|
var shot = false;
|
|
var oneshot;
|
|
var periodic;
|
|
periodic = new Timer.periodic(const Duration(milliseconds: 10), (timer) {
|
|
expect(shot, isFalse);
|
|
shot = true;
|
|
expect(timer, same(periodic));
|
|
periodic.cancel();
|
|
oneshot.cancel();
|
|
// Wait some more time to be sure callbacks won't be invoked any
|
|
// more.
|
|
new Timer(const Duration(milliseconds: 50), () {
|
|
replyTo.send('DONE');
|
|
});
|
|
});
|
|
// We launch the oneshot timer after the periodic timer. Otherwise a
|
|
// (very long) context switch could make this test flaky: assume the
|
|
// oneshot timer is created first and then there is a 30ms context switch.
|
|
// when the periodic timer is scheduled it would execute after the oneshot.
|
|
oneshot = new Timer(const Duration(milliseconds: 30), () {
|
|
fail('Should never be invoked');
|
|
});
|
|
} |