# Precompilation gridlock on HPC cluster

**URL:** <https://discourse.julialang.org/t/precompilation-gridlock-on-hpc-cluster/114213>\
**Category:** General Usage\
**Tags:** question\
**Created:** [May 14, 2024, 2:28am UTC](https://discourse.julialang.org/t/precompilation-gridlock-on-hpc-cluster/114213 "2024-05-14T02:28:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jling](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jling/32/212909_2.png) [@jling](https://discourse.julialang.org/u/jling)\
**Post date:** [May 14, 2024, 2:51am UTC](https://discourse.julialang.org/t/precompilation-gridlock-on-hpc-cluster/114213/2 "2024-05-14T02:51:28Z")

</div>

I might be jumping to conclusion a bit but at first glance it looks like a variant of:

- [Error precompiling on cluster](https://discourse.julialang.org/t/error-precompiling-on-cluster/104974/)
- [Precompilation Fails on HPC](https://discourse.julialang.org/t/precompilation-fails-on-hpc/104664)
- [Yet another precompilation-on-HPC issue](https://discourse.julialang.org/t/yet-another-precompilation-on-hpc-issue/105731/)

I think they started to pop up in 1.9 because that’s when we tightened the criteria for invalidation (i.e. more easily invalid)

and the solution is to play with `JULIA_CPU_TARGET` [`compilecache` failed when `@everywhere using` from remote machines · Issue #48217 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/issues/48217#issuecomment-1554149169)

---

_[View the full topic](https://discourse.julialang.org/t/precompilation-gridlock-on-hpc-cluster/114213)._