[mono][wasi] Stand up AOT tests in ci

dotnet / runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.

https://docs.microsoft.com/dotnet/core/

MIT License

15.47k stars 4.76k forks source link

[mono][wasi] Stand up AOT tests in ci #95136

Open lewing opened 1 year ago

lewing commented 1 year ago

[x] smoke tests (on runtime pipeline) [assigned: AJ]
[x] library tests (on runtime-wasm pipeline, same as what we have for browser-wasm) [assigned: AJ]
[x] wbt (Ankit's proposal from the comment) [assigned: IT]
[ ] runtime tests interpreter (Release AllSubsets_Mono_RuntimeTests monointerpreter) [assigned: IT]
[ ] runtime tests AOT

radical commented 1 year ago

We already have Wasi.Build.Tests, and that has one AOT test :D More should be added. For example:

[x] aot with single file bundle
[x] aot without single file bundle
[x] running an AOT'ed app (once that is working)

ghost commented 1 year ago

Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.

Issue Details

- [ ] smoke tests (on `runtime` pipeline) - [ ] library tests (on `runtime-wasm` pipeline, same as what we have for `browser-wasm`) - [ ] wbt - [ ] runtime tests

Author:	lewing
Assignees:	radical, ilonatommy
Labels:	`arch-wasm`, `area-Codegen-AOT-mono`, `os-wasi`
Milestone:	9.0.0

ilonatommy commented 1 year ago

What does "runtime tests" mean?

radical commented 1 year ago

What does "runtime tests" mean?

These are in src/tests. Note that we don't run wasm runtime tests with AOT either, yet.

radical commented 1 year ago

Instead of runtimetests with AOT, the first thing to do would be runtimetests with the interpreter. That is what we have for wasm right now.

You can look in src/tests for what we do for wasm. For example we have Common/wasm-test-runner/WasmTestRunner.proj, which you will probably need to duplicate for wasi. Look for TargetsBrowser to find out more about where we do custom things for wasm.