You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
iposva-google opened this issue
Jan 9, 2014
· 6 comments
Assignees
Labels
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.P1A high priority bug; for example, a single project is unusable or has many test failures
Every time the internal data structures in the VM change we need to invalidate existing snapshots as they are now incompatible.
A simple approach could be to bump the version number for every single official build.
More accurate, but significantly more involved would be to increase the version number whenever the information recorded in the snapshot changes. For example, generate a hash based on the VM internal data structures and core libraries flowing into the snapshot.
The text was updated successfully, but these errors were encountered:
iposva-google
added
Type-Defect
P1
A high priority bug; for example, a single project is unusable or has many test failures
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
labels
Aug 27, 2014
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.P1A high priority bug; for example, a single project is unusable or has many test failures
Every time the internal data structures in the VM change we need to invalidate existing snapshots as they are now incompatible.
A simple approach could be to bump the version number for every single official build.
More accurate, but significantly more involved would be to increase the version number whenever the information recorded in the snapshot changes. For example, generate a hash based on the VM internal data structures and core libraries flowing into the snapshot.
The text was updated successfully, but these errors were encountered: