Wasmtime: `cache_accounts_for_opt_level` failing on `main`

[fitzgen]

$ cargo test -p 'wasmtime' engine::tests::cache_accounts_for_opt_level
   Compiling wasmtime-environ v0.40.0 (/home/nick/wasmtime/crates/environ)
   Compiling wasmtime-runtime v0.40.0 (/home/nick/wasmtime/crates/runtime)
   Compiling wasmtime-cranelift v0.40.0 (/home/nick/wasmtime/crates/cranelift)
   Compiling wasmtime-jit v0.40.0 (/home/nick/wasmtime/crates/jit)
   Compiling wasmtime v0.40.0 (/home/nick/wasmtime/crates/wasmtime)
   Compiling wiggle v0.40.0 (/home/nick/wasmtime/crates/wiggle)
   Compiling wasi-common v0.40.0 (/home/nick/wasmtime/crates/wasi-common)
   Compiling wasi-cap-std-sync v0.40.0 (/home/nick/wasmtime/crates/wasi-common/cap-std-sync)
   Compiling wasmtime-wasi v0.40.0 (/home/nick/wasmtime/crates/wasi)
    Finished test [unoptimized + debuginfo] target(s) in 33.10s
     Running unittests src/lib.rs (target/debug/deps/wasmtime-c7705c65c4e36c46)

running 1 test
test engine::tests::cache_accounts_for_opt_level ... FAILED

failures:

---- engine::tests::cache_accounts_for_opt_level stdout ----
thread 'engine::tests::cache_accounts_for_opt_level' panicked at 'called `Result::unwrap()` on an `Err` value: ()', crates/jit/src/debug.rs:147:58
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    engine::tests::cache_accounts_for_opt_level

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 10 filtered out; finished in 0.03s

error: test failed, to rerun pass '-p wasmtime --lib'

[fitzgen]

This is my HEAD for main:

commit 301be7438e424a1bcaa5354ebe6d1b73b7f880ac (HEAD -> main, bytecodealliance/main)
Author: Trevor Elliott <telliott@fastly.com>
Date:   Wed Aug 3 13:28:52 2022 -0700

    x64: Begin migrating branch instructions to ISLE (#4587)
    
    https://github.com/bytecodealliance/wasmtime/pull/4587

[akirilov-arm]

I enabled this test on AArch64 in #3606, so after seeing this issue I thought that I had caused a regression, but I just checked, and the test passed when I ran it via ci/run-tests.sh; after that I changed one of the test assertions to use a bogus value to verify that the test was actually running. Curiously, it fails when executed directly, as specified here.

[alexcrichton]

Oh that explains why my bisection run on an AArch64 machine points to #3606 as the cause! A bisection on an x86_64 machine points to #4571 and while that is entirely unrelated I think I see the problem so I'll post a fix soon.