Processing of memory performance test results #11665
Conversation
github-actions
bot
added
area: build
alexvy86
force-pushed
the
memory-test-processing
branch
from
8c9a9f3
to
c8512ea
Compare
github-actions
bot
removed
the
dependencies
${{ variables.buildDirectory }} is a relative path, not absolute.
github-actions
bot
added
the
area: tests
|
@anthony-murphy , @curtisman , could you take a look at this one when you have a chance? |
| @@ -32,7 +31,7 @@ parameters: | |||
|
|
|||
| - name: poolBuild | |||
| type: object | |||
| default: Small | |||
There was a problem hiding this comment.
Because the time it takes for the repo to build (npm run ci:build) in Small vs Large is extremely different, 33m vs 5m. If we're fine letting this pipeline take much longer to run, we can change it back to Small, but I thought Large would be better. If we eventually move to a model where only 1 pipeline does the build and the rest work on its artifacts, this decision will go away 😄 .
There was a problem hiding this comment.
ah... we are still rebuilding in the pipeline. That make more sense.
We should switch back to small once (or if) we stop rebuilding.
|
This commit is queued for merging with the |
Description
Follow-up to #11622, for memory tests. Updates tools and pipelines to execute our memory usage tests and report results to Kusto.
Any relevant logs or outputs
A few successful pipeline runs here and here.
Results in Kusto
Execution time tests
Memory tests
Other information or known dependencies
Depends on #11661 .
AB 957