Remove invalid URI in an attempt to fix a windows bug.

pkg/analyzer/test/parse_compilation_unit_test.dart

Index: pkg/analyzer/test/parse_compilation_unit_test.dart
diff --git a/pkg/analyzer/test/parse_compilation_unit_test.dart b/pkg/analyzer/test/parse_compilation_unit_test.dart
index c5313da88c8d00b0b2ec0f50215f0a960522d2f6..710380f0def60f4d860bb89d842349bd94b32d39 100644
--- a/pkg/analyzer/test/parse_compilation_unit_test.dart
+++ b/pkg/analyzer/test/parse_compilation_unit_test.dart
@@ -26,14 +26,12 @@ void main() {
     })));
   });
 
-  test("defaults to '<unknown source>' if no name is provided", () {
+  test("defaults to 'null' if no name is provided", () {
     expect(() {
       parseCompilationUnit("void main() => print('Hello, world!')");
     }, throwsA(predicate((error) {
       return error is AnalyzerErrorGroup &&
-          error
-              .toString()
-              .contains("Error in <unknown source>: Expected to find ';'");
+          error.toString().contains("Error in null: Expected to find ';'");

[Paul Berry, 2016/03/01 17:14:32]

It seems like a shame to expose the user to the phrase "Error in null".

How about if we change AnalyzerError.toString() so that if
`error.source.shortName` is null, it defaults to '<unknown source>'?  That way
we would still avoid the Windows bug but user-visible behavior wouldn't be
degraded.

[Brian Wilkerson, 2016/03/02 16:31:00]

You're right, that is better. Done.

     })));
   });