Don't perform final fields and top-level variables type propagation.

pkg/analysis_server/test/completion_test.dart

Index: pkg/analysis_server/test/completion_test.dart
diff --git a/pkg/analysis_server/test/completion_test.dart b/pkg/analysis_server/test/completion_test.dart
index de88533b2720b0cb234a4b6e266436e826bd9fde..70ac85438ea320116b1c5b05e926239111a2926b 100644
--- a/pkg/analysis_server/test/completion_test.dart
+++ b/pkg/analysis_server/test/completion_test.dart
@@ -2850,7 +2850,7 @@ class A {
 
     // test analysis of untyped fields and top-level vars
     buildTests('test035', '''class Y {final x='hi';mth() {x.!1length;}}''',
-        <String>["1+length"]);
+        <String>["1+length"], failingTests: '1');

[Brian Wilkerson, 2016/08/29 20:49:03]

It seems odd to have a single test that is expected to fail. It seems better to
just remove the test.

[Paul Berry, 2016/08/29 20:53:35]

As a counterpoint to that, this is a test that we ought to be able to get to
pass once strong mode is the default.  Perhaps we should keep it until that
happens?

[scheglov, 2016/08/29 20:53:55]

I thought we might want to keep it to re-enable when we switch to strong mode by
default / as the only mode.

[Brian Wilkerson, 2016/08/29 21:13:24]

Why not just set strong mode for this one test? (I hope we have some way of
testing completion under strong mode!)

 
     // TODO(scheglov) decide what to do with Type for untyped field (not
     // supported by the new store)