# \[Bug\] Failed to compile Wasm that is known to be good

**URL:** <https://forum.dfinity.org/t/bug-failed-to-compile-wasm-that-is-known-to-be-good/270>\
**Category:** Command Line Tools\
**Created:** [December 8, 2019, 10:59am UTC](https://forum.dfinity.org/t/bug-failed-to-compile-wasm-that-is-known-to-be-good/270 "2019-12-08T10:59:25Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![alexa.smith](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/alexa.smith/32/21_2.png) [@alexa.smith](https://forum.dfinity.org/u/alexa.smith)\
**Post date:** [December 9, 2019, 5:17pm UTC](https://forum.dfinity.org/t/bug-failed-to-compile-wasm-that-is-known-to-be-good/270/3 "2019-12-09T17:17:14Z")

</div>

@guillaumestols see here from the team: Client tried to recover from a checkpoint created by the previous version of SDK. Killing the checkpoint will fix the problem. Something like `rm -rf $TMPDIR/checkpoints`. We’re also currently working on a longer-term fix!

---

_[View the full topic](https://forum.dfinity.org/t/bug-failed-to-compile-wasm-that-is-known-to-be-good/270)._