[wasm] CI: Add support for running WBT with multithreaded runtime installed too #89611
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
.. to be similar to the values in `src/mono/wasm/runtime/dotnet.d.ts`. The other values are not changed as the names in the tests map better to the terms used in the build. Based on feedback from @maraf .
.. preparing the required nugets for wbt
.. jobs.
- `wasm-build-only.yml`:
- Use the new `mono.wasmworkload` subset to prepare some nugets
needed for WBT
- Build WBT, and generate the zip file, but don't generate the sdk
- After the build, run:
- `wasm-post-build-steps.yml` - Publishes the nugets, some tasks
needed for WBT job, and archive of `Wasm.Build.Tests`.
This depends on two other builds: 1. A single threaded build run from wasm-build-only, which publishes its nugets, and other artifacts. 2. A multi threaded build The actual WBT job does not build anything now. Instead: 1. Downloads the artifacts from the two builds 2. Downloads Wasm.Build.Tests.zip 2. Sets up `artifacts/` to enable the steps below 3. Prepare the sdk for workload testing 4. Run the zip from (2) with sdk from (3).
ghost
added
the
|
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
radical
changed the title
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Notes for reviewers: Read the individual commits in order. |
|
@akoeplinger this has some non-wasm CI, and build bits. Would you mind taking a look? |
This was referenced Jul 28, 2023
|
the non-MT and the MT build still can't run on in the same |
|
Failures are known, and unrelated. |
Hm good question. I will disable the MT test for local runs right now. And in a follow up PR, add some detection mechanism so it runs only if you have a proper mt runtime available. |
pavelsavara
approved these changes
Jul 28, 2023
.. and complain if it is not available on CI.
|
Tagging subscribers to this area: @directhex Issue Details[wasm] CI: Add support for running WBT with multiple runtime packsThis depends on two other builds:
The actual WBT job does not build anything now. Instead:
Details
Notes
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[wasm] CI: Add support for running WBT with multiple runtime packs
This depends on two other builds:
The actual WBT job does not build anything now. Instead:
artifacts/to enable the steps belowDetails
mono.wasmworkloadsubsetNotes
dotnet.native.worker.js) is available