-
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] Add runtime-wasm-perf
pipeline
#72119
Conversation
/azp run perf-wasm |
Tagging subscribers to 'arch-wasm': @lewing Issue Detailsnull
|
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run perf-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run perf-wasm |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run perf-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run perf-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm,perf-wasm |
Azure Pipelines successfully started running 2 pipeline(s). |
.. `TrimMode=link`.
/azp run perf-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
4f36df2
to
5a679c2
Compare
Internal pipeline has a build for this branch - |
This seems useful, is there any reason not to do it? |
/azp run perf-wasm |
Azure Pipelines failed to run 1 pipeline(s). |
I didn't add it to |
/azp run perf-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
.. but this will be helpful irrespective, by running manually |
|
@akoeplinger @DrewScoggins any thoughts on this? |
@radical looks good but I'd prefer the AzDO pipeline name to be |
/azp run runtime-wasm-perf |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
perf-wasm
pipelineruntime-wasm-perf
pipeline
Confirmed that the pipeline can be triggered by the new name. And it doesn't affect |
This adds a new
runtime-wasm-perf
pipeline, which can be run manually with/azp run runtime-wasm-perf
Essentially, splits the perf jobs into
perf-wasm-jobs.yml
, andperf-non-wasm-jobs.yml
It does not change the existing perf pipeline
this will run all the wasm benchmarks, but it doesn't support comparing results yet
A follow up PR will add perf jobs to the runtime pipelines, for sanity check, and won't run the full set of benchmarks.