Testrunner for 3rd parties.

utils/testrunner/delete_task.dart

Index: utils/testrunner/delete_task.dart
===================================================================
--- utils/testrunner/delete_task.dart	(revision 0)
+++ utils/testrunner/delete_task.dart	(revision 0)
@@ -0,0 +1,21 @@
+// Copyright (c) 2012, 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.
+
+// A simeple pipeline task to delete a file.
+class DeleteTask extends PipelineTask {
+  String filenameTemplate;
+
+  DeleteTask(this.filenameTemplate);
+
+  void execute(Path testfile, List stdout, List stderr, bool verboseLogging,
+              Function exitHandler) {
+    var fname = concretize(filenameTemplate, testfile);

[Siggi Cherem (dart-lang), 2012/08/29 01:05:55]

it seems that in some of the tasks the macros are not helping that much. For
instance, you could directly delete the file under the path, rather than
reconstructing the path from the filename. 

[gram, 2012/08/29 20:12:26]

No, the macro is important. The concrete testfile here is the original test file
(e.g. pkg/unittest/tests/matchers_test.dart). The macro will expand to various
related transient files, e.g. /tmp/testrunner/matchers_test.css. 

+    var f = new File(fname);
+    f.deleteSync();

[Siggi Cherem (dart-lang), 2012/08/29 01:05:55]

given that this is already an async task, you could use the async API here too
:)

[gram, 2012/08/29 20:12:26]

Yes, but my expectation is that the underlying OS functions for file deletion
(like unlink()) are sync, and thus making file deletion async is unnatural and
just Dart weirdness, that I see no reason to perpetuate :-)

+    if (verboseLogging) {
+      stdout.add('Removing $fname');
+    }
+    exitHandler(0);
+  }
+}