Skip to content

Some tests give different results from run-to-run on the same machine #5334

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.

Sign up for GitHub

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

Jump to bottom
Closed
6 tasks
mdboom opened this issue Oct 27, 2015 · 2 comments
Closed
6 tasks

Some tests give different results from run-to-run on the same machine #5334

mdboom opened this issue Oct 27, 2015 · 2 comments
Labels
status: inactive Marked by the “Stale” Github Action

Comments

@mdboom
Copy link
Member

mdboom commented Oct 27, 2015

The likely cause is a dictionary somewhere that causes the drawing order to be non-deterministic.

I found these in #5307, but decided to punt on resolving them for now -- instead just increasing the tolerance on those tests. This is a reminder that we may want to go back and investigate this at a later date.

The tests are:

  • test_axes_grid1:test_twin_axes_empty_and_removed
  • test_axes:test_boxplot
  • test_axes:test_boxplot_rc_parameters
  • test_axes:test_specgram_freqs
  • test_axes:test_specgram_noise
  • test_axes:test_specgram_magnitude_freqs
@mdboom mdboom mentioned this issue Oct 27, 2015
Merged
@tacaswell
Copy link
Member

boxplot is on the list of things to be converted to improved container artists (ex #3944)

@github-actions
Copy link

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Mar 17, 2023
@jklymak jklymak closed this as completed Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: inactive Marked by the “Stale” Github Action
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mdboom @tacaswell @jklymak