Closed itziakos closed 9 years ago
Good news: I can reproduce 2) on my machine
So the errors from 2) are coming from enable
and was introduced in
https://github.com/enthought/enable/commit/bd86c7c9637ea99e164b39fe5bb407fc96821800 .
As it is now, mouse_move
assumes that the window is always a mock one (https://github.com/enthought/enable/commit/bd86c7c9637ea99e164b39fe5bb407fc96821800), while we're passing a real window.
The errors can be worked around by using the mock window, i.e., removing window=editor.window
in
https://github.com/enthought/ensemble/blob/4511335b42821dfd861183707bbf57438da4df31/ensemble/ctf/tests/test_editor.py#L57
and
https://github.com/enthought/ensemble/blob/4511335b42821dfd861183707bbf57438da4df31/ensemble/ctf/tests/test_editor.py#L64
OTOH the tests in TestEditor
do not check anything, and always pass unless something bad happend just interacting with the window, so maybe having a mock one would make them even more permissive.
Looking good now that #43 is in. I'm not sure how y'all feel about the volume renderer test "errors", but they don't really bother me. :+1: @pberkes, @itziakos: Merge when you're satisfied with the state of this branch.
LGTM
@itziakos @jwiggins Any lead on why the tests might be failing? I'd like to give a hand to see this issue fixed ASAP.
At the moment there are two kind of problems:
1) errors that do not break the tests and that look like this:
2) Errors from
enable
: