Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

TST: Remove memory leak test#27732

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
ksunden merged 1 commit intomatplotlib:mainfromQuLogic:no-leak-test
Feb 5, 2024
Merged

Conversation

QuLogic
Copy link
Member

PR summary

It is flaky, and our memory "limit" is pretty much arbitrary. Testing withtools/memleak.py shows that memory usage generally rises and only stabilizes close to 200 figures, while this test only does a warmup of 2 figures. Waiting for equilibrium would take too long for a general test, so we might move this to a weekly job later.

For example, withjust Agg:
agg

and with the flaky wxAgg:
wxagg

It's true that the latter uses more memory, but it still takes about 200 or so figure to reach equilibrium.

Closes#27635

PR checklist

It is flaky, and our memory "limit" is pretty much arbitrary. Testingwith `tools/memleak.py` shows that memory usage generally rises and onlystabilizes close to 200 figures, while this test only does a warmup of2 figures. Waiting for equilibrium would take too long for a generaltest, so we might move this to a weekly job later.
@QuLogicQuLogic added this to thev3.9.0 milestoneFeb 1, 2024
@richardsheridan
Copy link
Contributor

I'd be on board with a weekly run that's not tied to PRs. After all we're not really worried about any specific threshold, just if things are growing excessively, and a weekly trend would be easy to bisect, at least compared to bug reports.

Maybe it would be worth putting together a whole pythonspeed thing with benchmarks and memory usage?

@dstansby
Copy link
Member

I presume the x-axis in those plots is elapsed time in seconds? I'm 👍 to removing these to stop the CI failing for now given it doesn't seem like there's an easy or quick fix to the tests, but would be worth opening an issue to discuss ways to fix these tests or add replacement memory leak tests.

@tacaswell
Copy link
Member

I presume the x-axis in those plots is elapsed time in seconds?

The x-axis is cycle count (so how many Figures we have created and destroyed).

@ksundenksunden merged commite470c70 intomatplotlib:mainFeb 5, 2024
@QuLogicQuLogic deleted the no-leak-test branchFebruary 5, 2024 21:38
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@tacaswelltacaswelltacaswell approved these changes

@ksundenksundenksunden approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v3.9.0
Development

Successfully merging this pull request may close these issues.

[Bug]: test_figure_leak_20490 repeatedly failing on CI
5 participants
@QuLogic@richardsheridan@dstansby@tacaswell@ksunden

[8]ページ先頭

©2009-2025 Movatter.jp