# Warning: Runtime invalidation was disabled, but the CPU info is out-of-date

**URL:** https://discourse.julialang.org/t/warning-runtime-invalidation-was-disabled-but-the-cpu-info-is-out-of-date/134519
**Category:** General Usage
**Tags:** cpu
**Created:** [December 12, 2025, 3:08pm UTC](https://discourse.julialang.org/t/warning-runtime-invalidation-was-disabled-but-the-cpu-info-is-out-of-date/134519 "2025-12-12T15:08:19Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Ju\_ska](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@Ju\_ska](https://discourse.julialang.org/u/Ju_ska)
#### Post date: [December 12, 2025, 3:08pm UTC](https://discourse.julialang.org/t/warning-runtime-invalidation-was-disabled-but-the-cpu-info-is-out-of-date/134519/1 "2025-12-12T15:08:19Z")

</div>

Hi,

I’m using the $JULIA\_CPU\_TARGET variable with Julia 1.12.2.  
Some time ago, I started to get this message when updating the packages:

HostCPUFeatures  
│ ┌ Warning: Runtime invalidation was disabled, but the CPU info is out-of-date.  
│ │ Will continue with incorrect CPU feature flag: x86\_64\_avx2.  
│ └ @ HostCPUFeatures ~/.julia/packages/HostCPUFeatures/ZTXz4/src/cpu\_info\_x86.jl:49  
│ ┌ Warning: Runtime invalidation was disabled, but the CPU info is out-of-date.  
│ │ Will continue with incorrect CPU feature flag: x86\_64\_bmi2.  
│ └ @ HostCPUFeatures ~/.julia/packages/HostCPUFeatures/ZTXz4/src/cpu\_info\_x86.jl:49  
│ ┌ Warning: Runtime invalidation was disabled, but the CPU info is out-of-date.  
│ │ Will continue with incorrect CPU feature flag: x86\_64\_fma.  
│ └ @ HostCPUFeatures ~/.julia/packages/HostCPUFeatures/ZTXz4/src/cpu\_info\_x86.jl:49  
│ ┌ Warning: Runtime invalidation was disabled, but the CPU info is out-of-date.  
│ │ Will continue with incorrect CPU feature flag: x86\_64\_avx.  
│ └ @ HostCPUFeatures ~/.julia/packages/HostCPUFeatures/ZTXz4/src/cpu\_info\_x86.jl:49  
└

Any thoughts about this ?

---

<div class="post-metadata">

### Author: ![dubosipsl](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dubosipsl/32/52998_2.png) [@dubosipsl](https://discourse.julialang.org/u/dubosipsl)
#### Post date: [February 7, 2026, 2:17pm UTC](https://discourse.julialang.org/t/warning-runtime-invalidation-was-disabled-but-the-cpu-info-is-out-of-date/134519/2 "2026-02-07T14:17:30Z")

</div>

I have seen warning this recently in a Gitlab CI job but on Julia 1.10. What I did is to add a `LocalPreferences.toml` in my `test` folder with:

```julia-auto
[HostCPUFeatures]
allow_runtime_invalidation = true

```

and in the `runtest.jl` I do

```julia-auto
import HostCPUFeatures
@assert HostCPUFeatures.allow_eval

```

to make sure the preferences have taken effect.  
As to why this appeared, no idea.

---

<div class="post-metadata">

### Author: ![mattsignorelli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mattsignorelli/32/221502_2.png) [@mattsignorelli](https://discourse.julialang.org/u/mattsignorelli)
#### Post date: [March 20, 2026, 11:43am UTC](https://discourse.julialang.org/t/warning-runtime-invalidation-was-disabled-but-the-cpu-info-is-out-of-date/134519/3 "2026-03-20T11:43:31Z")

</div>

OK I had this issue just now, and found that deleting the Github actions cache for the particular failing runner worked: [Managing caches - GitHub Docs](https://docs.github.com/en/actions/how-tos/manage-workflow-runs/manage-caches)