Skip to content

Warning: Tried to initialize from a previous compilation #35866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
goderbauer opened this issue Feb 5, 2019 · 3 comments
Closed

Warning: Tried to initialize from a previous compilation #35866

goderbauer opened this issue Feb 5, 2019 · 3 comments
Labels
legacy-area-front-end Legacy: Use area-dart-model instead.

Comments

@goderbauer
Copy link
Contributor

During a flutter test run I got the following message. Reported here as requested.

Compiler message:
Warning: Tried to initialize from a previous compilation (file:///Users/goderbauer/dev/flutter/packages/flutter/build/testfile.dill), but the file was not self-contained. This might be a bug.

The Dart team would greatly appreciate it if you would take a moment to report this problem at http://dartbug.com/new.
If you are comfortable with it, it would improve the chances of fixing any bug if you included the file file:///var/folders/t2/r2h8ytq53_x45hn80bhpb0ww0044f6/T/initialize_from.dillVuR3Vz/initialize_from.dill.gz in your error report, but be aware that this file includes your source code.
Either way, you should probably delete the file so it doesn't use unnecessary disk space.

initialize_from.dill.gz

@goderbauer
Copy link
Contributor Author

See also: #35695, #35476

@jensjoha
Copy link
Contributor

flutter/engine@1946082 was done at around the time this bug was submitted.
Is it possible that you checked out a (slightly) older version of flutter, and then tested with that?

If the initialize-from-dill file was created with a version on or after flutter/flutter@9b053dd and you then went back to a version of flutter before flutter/flutter@b5e0973, we cannot initialize from the dill because the assumed sdk-file doesn't include the "enum Brightness" (we cannot find root::dart:ui::Brightness).

We certainly need a mechanism to catch stuff like this. I created #36032 for that.

@jensjoha
Copy link
Contributor

jensjoha commented Apr 4, 2019

I'll assume the above was correct. #36032 was created to remedy such situations (although its still not fixed).

@jensjoha jensjoha closed this as completed Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy-area-front-end Legacy: Use area-dart-model instead.
Projects
None yet
Development

No branches or pull requests

3 participants