# Seemingly Random Precompilation Errors: "does not support precompilation but is imported by a module that does"

**URL:** https://discourse.julialang.org/t/seemingly-random-precompilation-errors-does-not-support-precompilation-but-is-imported-by-a-module-that-does/360
**Category:** General Usage
**Created:** [November 16, 2016, 4:49pm UTC](https://discourse.julialang.org/t/seemingly-random-precompilation-errors-does-not-support-precompilation-but-is-imported-by-a-module-that-does/360 "2016-11-16T16:49:15Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)
#### Post date: [November 16, 2016, 9:18pm UTC](https://discourse.julialang.org/t/seemingly-random-precompilation-errors-does-not-support-precompilation-but-is-imported-by-a-module-that-does/360/6 "2016-11-16T21:18:59Z")

</div>

Do tests (`Pkg.test`) run in a separate process that stay open? I’ve had it before where I couldn’t get tests to not mess up like this, even though I had quit out of the REPL/Atom.

Good to see I’m not alone on this though. I thought it might’ve just been me 🙂

---

_[View the full topic](https://discourse.julialang.org/t/seemingly-random-precompilation-errors-does-not-support-precompilation-but-is-imported-by-a-module-that-does/360)._