Tests failing on latest SDK

[kevmoo]

https://travis-ci.org/dart-lang/dart2_fix/builds/410955962

Are things broken on SDKs w/out the old constants, @devoncarew ?

[devoncarew]

Yes, looking at this:

• we don't try and update code with analysis errors
• we key off the places in code where the analysis server reports deprecation messages

Removing the deprecated constants from the SDK breaks both of those assumptions. We should update the docs for this tool to state that it can only be run on an sdk after the depreciations were introduced, and before the constants were removed.

[kevmoo]

...right. And set the SDK constraint and the travis config accordingly?

…

On Thu, Aug 2, 2018 at 6:23 AM Devon Carew ***@***.***> wrote: Yes, looking at this: - we don't try and update code with analysis errors - we key off the places in code where the analysis server reports deprecation messages Removing the deprecated constants from the SDK breaks both of those assumptions. We should update the docs for this tool to state that it can only be run on an sdk after the depreciations were introduced, and before the constants were removed. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#40 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABCivLfYzsXBIU87aUTUvxh_WY7LGvCks5uMv08gaJpZM4VrjAa> .

[devoncarew]

I updated the docs (98f0833), but this is a sticky situation. We either need much longer deprecation periods, or our migration tools should be entirely regex based.