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

Fix for unexpected test code #374

Merged

Conversation

stefanoborini
Copy link
Contributor

Fix for a few strange things. The dictionary is changed in place, so it must be copied.
Additionally, it's probably supposed to call tearDown, not setUp()

Fix for a few strange things. The dictionary is changed in place, so it must be copied.
Additionally, it's probably supposed to call tearDown, not setUp()
@kitchoi
Copy link
Contributor

kitchoi commented May 3, 2016

Can you specify which tests fail, if possible?

@stefanoborini
Copy link
Contributor Author

This one, but it only fails on OSX for some reason.

======================================================================
ERROR: Test probe_data
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/travis/build/enthought/mayavi/mayavi/tests/test_mlab_integration.py", line 236, in tearDown
    for engine in registry.engines:
RuntimeError: dictionary changed size during iteration

else:
for engine in registry.engines:
for engine in registry.engines[:]:
Copy link
Contributor

@kitchoi kitchoi May 3, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You meant list(registry.engines)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kitchoi it's the same, but I just realized it's a dictionary, not a list.

@kitchoi
Copy link
Contributor

kitchoi commented May 3, 2016

less_than_vtk_5_6 is not what it looks! it is in fact less_than_vtk_5_10!

@codecov-io
Copy link

codecov-io commented May 3, 2016

Current coverage is 45.51%

Merging #374 into master will not change coverage

@@             master       #374   diff @@
==========================================
  Files           254        254          
  Lines         22885      22885          
  Methods           0          0          
  Messages          0          0          
  Branches       3027       3027          
==========================================
  Hits          10414      10414          
  Misses        11756      11756          
  Partials        715        715          

Powered by Codecov. Last updated by 503c807...d21739b

@@ -211,29 +211,29 @@ def test_colorbar(self):
################################################################################
class TestMlabPipeline(TestMlabNullEngine):
""" Test the pipeline functions.
For vtk versions greater than 5.6 (5.10.1 onwards), widgets need
For vtk versions greater than 5.10.1, widgets need
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is 5.10.0 a thing?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can safely assume that patchlevel is irrelevant (hopefully)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. So perhaps 5.10 onwards is more true to the implementation in the code.

@stefanoborini
Copy link
Contributor Author

Failure seems unrelated, restarting.

@kitchoi
Copy link
Contributor

kitchoi commented May 3, 2016

Assuming tests would pass with Linux + 5.10 (as it does with Mac), it looks good to me

@stefanoborini
Copy link
Contributor Author

Tested on 5.10 ubuntu, seems to work. Merging.

@stefanoborini stefanoborini merged commit 4ad6afa into master May 3, 2016
@stefanoborini stefanoborini deleted the feature/fix-for-unexpected-test-code-0503-1349 branch May 3, 2016 16:08
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.

None yet

3 participants