-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wasm] Split runtime-wasm
pipeline into runtime-wasm-libtests
, and runtime-wasm-non-libtests
#74859
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue Detailsnull
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-libtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-libtests,runtime-wasm |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run runtime-wasm-libtests,runtime-wasm,runtime-wasm-non-libtests |
Azure Pipelines successfully started running 2 pipeline(s), but failed to run 1 pipeline(s). |
/azp run runtime-wasm-libtests,runtime-wasm,runtime-wasm-non-libtests |
Azure Pipelines successfully started running 3 pipeline(s). |
a4bf18d
to
9669e83
Compare
/azp run runtime-wasm-libtests,runtime-wasm,runtime-wasm-non-libtests |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
9669e83
to
4c4bc3d
Compare
/azp run runtime-wasm-libtests,runtime-wasm,runtime-wasm-non-libtests,runtime-extra-platforms |
Azure Pipelines successfully started running 4 pipeline(s). |
6e701d7
to
7ad8e68
Compare
runtime-wasm
pipelineruntime-wasm
pipeline into runtime-wasm-libtests
, and runtime-wasm-non-libtests
/azp run runtime-wasm-libtests,runtime-wasm,runtime-wasm-non-libtests,runtime-extra-platforms |
Azure Pipelines successfully started running 4 pipeline(s). |
/azp run runtime-wasm-libtests,runtime-wasm,runtime-wasm-non-libtests,runtime-extra-platforms |
Azure Pipelines successfully started running 4 pipeline(s). |
e93f943
to
7ad8e68
Compare
7ad8e68
to
7cf965a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I don't love the runtime-wasm-non-libtests
name but I couldn't come up with a better name either :)
And we might end up doing more splits, depending on usage :) |
Adds two new pipelines:
runtime-wasm-libtests
- runs all the wasm library testsruntime-wasm-non-libtests
- runs all the wasm non-library tests like WBT, debugger etc.And
runtime-wasm
runs the combination of the two above.runtime
) pipelineWhich pipeline should I run?
runtime
didn't run the tests that would be useful for testing the changes, then:runtime-wasm-libtests
Wasm.Build.Tests
, or debugger tests, or runtime tests, then useruntime-wasm-non-libtests
runtime-wasm
when you want to run all the wasm testsUpdated CI matrix for wasm
PR:
only-pc
meansonly on relevant path changes
Run by default
runtime
runs jobs only when relevant paths change. And forAOT
, only smoke tests are run.Run manually with
/azp run ..
runtime-wasm*
pipelines are triggered manually, and they only run the jobs that would not run on any default pipelines based on path changes.AOT
jobs run only smoke tests onruntime
, and onruntime-wasm*
pipelines all theAOT
tests are run.runtime-extra-platforms
does not run any wasm jobs on PRshigh resource aot
runs a few specific library tests with AOT, that require more memory to AOT.Rolling build (twice a day):
runtime
runs all the wasm jobs, butAOT
still only runs smoke tests.runtime-extra-platforms
also runs by default. And it runs only the cases not covered byruntime
.high resource aot
runs a few specific library tests with AOT, that require more memory to AOT.