Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(310)

Issue 2883533002: Update expectations files to get more strong mode inference tests to pass. (Closed)

Created:
3 years, 7 months ago by Paul Berry
Modified:
3 years, 7 months ago
CC:
reviews_dartlang.org, dart-fe-team+reviews_google.com
Target Ref:
refs/heads/master
Visibility:
Public.

Description

Update expectations files to get more strong mode inference tests to pass. The logic to make these tests pass was already in place, but their expectations files either didn't exist or needed tweaking. R=scheglov@google.com, sigmund@google.com Committed: https://github.com/dart-lang/sdk/commit/fe991b20dd8795950239e81a9ed966502a6f3ebd

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+135 lines, -18 lines) Patch
M pkg/front_end/test/fasta/strong.status View 3 chunks +0 lines, -8 lines 0 comments Download
M pkg/front_end/testcases/inference/generic_methods_correctly_recognize_generic_upper_bound.dart.strong.expect View 1 chunk +1 line, -1 line 0 comments Download
A pkg/front_end/testcases/inference/generic_methods_do_not_infer_invalid_override_of_generic_method.dart.strong.expect View 1 chunk +22 lines, -0 lines 0 comments Download
A pkg/front_end/testcases/inference/generic_methods_handle_override_of_non_generic_with_generic.dart.strong.expect View 1 chunk +26 lines, -0 lines 0 comments Download
A pkg/front_end/testcases/inference/generic_methods_infer_generic_method_type.dart.strong.expect View 1 chunk +22 lines, -0 lines 0 comments Download
A + pkg/front_end/testcases/inference/infer_generic_method_type_required.dart.strong.expect View 1 chunk +4 lines, -4 lines 0 comments Download
M pkg/front_end/testcases/inference/propagate_inference_to_field_in_class_dynamic_warnings.dart View 1 chunk +1 line, -1 line 0 comments Download
A + pkg/front_end/testcases/inference/propagate_inference_to_field_in_class_dynamic_warnings.dart.strong.expect View 1 chunk +6 lines, -4 lines 0 comments Download
M pkg/front_end/testcases/inference/propagate_inference_transitively.dart View 1 chunk +2 lines, -0 lines 0 comments Download
A pkg/front_end/testcases/inference/propagate_inference_transitively.dart.strong.expect View 1 chunk +17 lines, -0 lines 0 comments Download
A pkg/front_end/testcases/inference/propagate_inference_transitively2.dart.strong.expect View 1 chunk +34 lines, -0 lines 0 comments Download

Messages

Total messages: 8 (2 generated)
Paul Berry
3 years, 7 months ago (2017-05-12 18:05:37 UTC) #2
scheglov
LGTM
3 years, 7 months ago (2017-05-12 18:08:12 UTC) #3
Siggi Cherem (dart-lang)
lgtm - I'm not sure why didn't we see these failures before locally or on ...
3 years, 7 months ago (2017-05-12 18:16:15 UTC) #4
Paul Berry
On 2017/05/12 18:16:15, Siggi Cherem (dart-lang) wrote: > lgtm - I'm not sure why didn't ...
3 years, 7 months ago (2017-05-12 18:20:04 UTC) #5
Paul Berry
Committed patchset #1 (id:1) manually as fe991b20dd8795950239e81a9ed966502a6f3ebd (presubmit successful).
3 years, 7 months ago (2017-05-12 18:20:25 UTC) #7
Siggi Cherem (dart-lang)
3 years, 7 months ago (2017-05-12 18:35:26 UTC) #8
Message was sent while issue was closed.
On 2017/05/12 18:20:04, Paul Berry wrote:
> On 2017/05/12 18:16:15, Siggi Cherem (dart-lang) wrote:
> > lgtm - I'm not sure why didn't we see these failures before locally or on
the
> > bots?
> 
> It's because the expectation files were wrong, and the status files said
"Fail",
> so the tests failed as expected.  Unfortunately this is one of the drawbacks
of
> the "golden file" approach--when we fix a test but the expectation file has a
> problem, we don't get any feedback from the bot.
> 
> (I discovered these tests by re-running the tests with
-DupdateExpectations=true
> -DskipVm=true, which caused the tests to pass.)
> 
> Incidentally, I'm planning to have a conversation with Peter sometime next
week
> to see if we can add more types of expectations to the status file so that
when
> a test starts failing for a different reason, we notice.

that makes sense - +1 on adding more types. My understanding is that
VerificationError is a recent addition, and it should be fairly simple to add
more.

Powered by Google App Engine
This is Rietveld 408576698