Skip to content
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

[Build] Adding memory leak tests using heap snapshots #13016

Merged
merged 9 commits into from
Sep 23, 2022
Merged

[Build] Adding memory leak tests using heap snapshots #13016

merged 9 commits into from
Sep 23, 2022

Conversation

RaananW
Copy link
Member

@RaananW RaananW commented Sep 22, 2022

This adds heap based memory leak tests during integration tests. Using memlab under the hood.

@azure-pipelines
Copy link

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

@azure-pipelines
Copy link

Reviewer - this PR has made changes to one or more package.json files.

@azure-pipelines
Copy link

@azure-pipelines
Copy link

Reviewer - this PR has made changes to one or more package.json files.

@azure-pipelines
Copy link

Reviewer - this PR has made changes to one or more package.json files.

@azure-pipelines
Copy link

Reviewer - this PR has made changes to one or more package.json files.

@RaananW RaananW marked this pull request as ready for review September 23, 2022 13:12
@RaananW RaananW merged commit bea1b49 into BabylonJS:master Sep 23, 2022
@RaananW RaananW deleted the memlabTests branch September 23, 2022 17:54
RaananW added a commit that referenced this pull request Dec 9, 2022
* introducing heap-based memory leak tests

* fix for CI

* wait for scene to be ready

* wait for scene to be ready

* wait for scene

* faster execution

* fix a leak

* formatting

* Dude...

Former-commit-id: 9c96d1e507706d85b5daca06ff17ec1a925f56f5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants