CI: Add memory usage regression monitoring for pull requests #1415
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
larabr
commented
Sep 9, 2021
larabr
force-pushed
the
ci-benchmark-memory-base
branch
from
60f7b4b
to
c1bc281
Compare
# Conflicts: # .github/workflows/benchmark.yml
larabr
force-pushed
the
ci-benchmark-memory-base
branch
from
c1bc281
to
ac6c2a4
Compare
twiss
approved these changes
Oct 15, 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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #403 : add tests to monitor memory usage of message encryption and decryption. Each test is run in a separate V8 instance, to make the result as deterministic as possible (streaming tests give false positives from time to time, but these should be easy to verify by re-running the workflow).
The tests are run on pull requests:
For example workflow behaviour and alert comments, see: larabr@a628975 and larabr#4
TODO: