This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Backport of ui: add memory usage ouput to ember-build-tests CI job into release/0.5.x
#2294
Conversation
This file contains 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
hc-github-team-waypoint
deleted the
backport/ui/jw-debug-build/brightly-champion-kite
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport
This PR is auto-generated from #2291 to be assessed for backporting due to the inclusion of the label backport/0.5.x.
The below text is copied from the body of the original PR.
Why the change?
This comes from the investigation of #2260, is based on @izaaklauer’s sage suggestion to record memory usage from our troublesome CI job so we can track it over time.
What does it look like?
Take a look at the CI run for this PR. Something like this:
Any downsides?
I don’t think so. It’s a negligible amount of extra work for the CI environment, makes our CI config only marginally more complicated, and gives us some valuable information.