Karan Lokchandani

@teyahb8 this is certainly very curious situation for JIT mode on linux, did you compile wasmedge from source or did you use the precompiled binary from releases or installed using...

@itowlson I've squashed all necessary changes. For context, all previous runs of all-integration-tests were executed on ubuntu-latest, which allowed them to run on my fork's PRs. However, I've now switched...

Everything is in place and all the tests pass, waiting for your review @itowlson

> Bother, that's a flake in MQTT. I saw you updated the settings for Postgres; do you think something similar needs to be done for MQTT? yeah this is my...

Update: I attempted to reproduce the flake on a fork using the ubuntu-latest runner ([link](https://github.com/PhantomInTheWire/spin/actions/runs/15758246560/attempts/7?pr=4)), running 20 jobs concurrently across multiple attempts but couldn’t trigger the issue(it did fail once...

I tried to reproduce this, and they no longer appear to be flaky. any way to reproduce this? cc: @kate-goldenring

Following up with more context on my attempt to reproduce this: - **OS:** macOS 15.5(Apple Silicon, arm64) - **Steps Taken:** - I enabled the previously ignored tests by modifying `tests/runtime.rs`...

Thanks, @itowlson — that makes sense! I’ved opened a PR with the tests re-enabled and monitor the CI runs for any flakiness.