DEV: Print usedJSHeapSize to the console after QUnit run #14462
Merged
Conversation
This is `console.log`'d to the browser console. run-qunit will print this to stdout. testem will not, so a custom reporter is implemented to print this message. The `--enable-precise-memory-info` is added so that chrome provides high-resolution memory information. This API is not supported by firefox. The logic will degrade gracefully.
CvX
approved these changes
Sep 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is
console.log
'd to the browser console. run-qunit will print this to stdout. testem will not, so a custom reporter is implemented to print this message.The
--enable-precise-memory-info
is added so that chrome provides high-resolution memory information. This API is not supported by firefox. The logic will degrade gracefully.TestEm output:
Run-qunit output:
The text was updated successfully, but these errors were encountered: