Stream: git-wasmtime

Topic: wasmtime / PR #11777 CI: Add SDE (emulator) to CI

Wasmtime GitHub notifications bot (Oct 01 2025 at 23:50):

rahulchaphalkar opened PR #11777 from rahulchaphalkar:sde-emulator-pr to bytecodealliance:main:

Adds Intel SDE to the CI in preparation of testing new instructions like APX, which are not available in QEMU.
SDE only tests wasmtime-tools for now, via crate field in config.
Have disabled sharding when crate field is present, assumption for now is this would only list few crates (1 in this case).
Uses following action to setup SDE - https://github.com/petarpetrovt/setup-sde

SDE Tests get triggered with a prtest:sde commit message, similar to some other components.

• prtest:sde will only run sde tests
• prtest:full will run everything _except_ sde tests
• prtest:full + prtest:sde will run all tests including sde tests

The env variables like WASMTIME_TEST_NO_SDE are introduced (similar to Qemu) to provide a clean way to disable any tests that are problematic, but are not being used right now. Can remove them if needed.

@jlb6740 @abrown

Wasmtime GitHub notifications bot (Oct 01 2025 at 23:50):

rahulchaphalkar requested pchickey for a review on PR #11777.

Wasmtime GitHub notifications bot (Oct 01 2025 at 23:50):

rahulchaphalkar requested wasmtime-default-reviewers for a review on PR #11777.

Wasmtime GitHub notifications bot (Oct 02 2025 at 14:32):

alexcrichton created PR review comment:

For this we have enough concurrency that it's ok to omit this. Basically it's fine to run by default on CI, and I'm at least personally otherwise wary of not running it by default as it means it would likely bitrot pretty quickly.

Wasmtime GitHub notifications bot (Oct 02 2025 at 14:32):

alexcrichton submitted PR review:

Thanks! One thing this might be useful for is the avx512 lowerings which probably aren't tested much on CI right now. Could you confirm that our avx512 runtests are running in the SDE?

Wasmtime GitHub notifications bot (Oct 02 2025 at 14:32):

alexcrichton created PR review comment:

Does this do much more than a curl + tar command? If so could this be manually done instead of using a 3rd-party action?

Wasmtime GitHub notifications bot (Oct 03 2025 at 18:17):

rahulchaphalkar commented on PR #11777:

Thanks! One thing this might be useful for is the avx512 lowerings which probably aren't tested much on CI right now. Could you confirm that our avx512 runtests are running in the SDE?

@alexcrichton I was looking into this to have a definite answer, and here's where I am thus far -

• There are 4 runtests which include some variant of avx512 like has_avx512f, has_avx512vl etc.
• I am testing these out locally on a system with AVX512 present (ICX) with RUST_LOG=trace, just natively without SDE
• I see SSE and AVX instructions in the log, but not AVX512. I tested by modifying a clif test (simd-shuffle.clif) to only include has_avx512vl and variants (and remove sse, avx etc) and I don't see any vshufps instructions. When I include has_avx then I do see vshufps.

With SDE -

• I tested in a similar way with SDE, and have same results. When I configure SDE with a platform without AVX support, then I see just shufps as expected from SSE, and configured with AVX capable platform, I see vshufps.

I also checked this with the python script that CI uses to kick things off, ./ci/run-tests.py with and without SDE.
To summarize, I do think AVX512 tests from runtests are being run, and the results match with and without SDE, but I am not sure if AVX512 instructions are being generated or not (doesn't look like it) for either case.

Wasmtime GitHub notifications bot (Oct 03 2025 at 18:23):

alexcrichton commented on PR #11777:

Thanks for investigating! That matches what my rough expectations would be, so I think it's safe to conclude "yep working as intended"

Wasmtime GitHub notifications bot (Oct 03 2025 at 18:55):

rahulchaphalkar updated PR #11777.

Wasmtime GitHub notifications bot (Oct 03 2025 at 19:01):

rahulchaphalkar submitted PR review.

Wasmtime GitHub notifications bot (Oct 03 2025 at 19:01):

rahulchaphalkar created PR review comment:

Done, doing it manually similar to qemu now.

Wasmtime GitHub notifications bot (Oct 03 2025 at 19:01):

rahulchaphalkar submitted PR review.

Wasmtime GitHub notifications bot (Oct 03 2025 at 19:01):

rahulchaphalkar created PR review comment:

Sure, removed it, now sde tests should run with full ci run

Wasmtime GitHub notifications bot (Oct 03 2025 at 19:02):

rahulchaphalkar edited PR #11777:

Adds Intel SDE to the CI in preparation of testing new instructions like APX, which are not available in QEMU.
SDE only tests wasmtime-tools for now, via crate field in config.
Have disabled sharding when crate field is present, assumption for now is this would only list few crates (1 in this case).
Uses following action to setup SDE - https://github.com/petarpetrovt/setup-sde

SDE Tests get triggered with a prtest:sde commit message, similar to some other components.

• prtest:sde will only run sde tests
• prtest:full will run everything _except_ sde tests
• prtest:full + prtest:sde will run all tests including sde tests

The env variables like WASMTIME_TEST_NO_SDE are introduced (similar to Qemu) to provide a clean way to disable any tests that are problematic, but are not being used right now. Can remove them if needed.

@jlb6740 @abrown
Edit -
Based off feedback below, SDE tests now run with a full CI run as well, previously they were filtered out and only ran for prtest:sde. Now they run for prtest:sde as well as prtest:full.

Wasmtime GitHub notifications bot (Oct 03 2025 at 19:18):

alexcrichton submitted PR review.

Wasmtime GitHub notifications bot (Oct 03 2025 at 19:41):

alexcrichton merged PR #11777.

Last updated: Dec 06 2025 at 06:05 UTC