Setup Appveyor#445
Conversation
new file: appveyor-clean-cache.txt new file: appveyor-run.cmd new file: appveyor.yml new file: install-edm-windows.cmd
modified: appveyor.yml
|
Note that both the 3.5 and 3.6 appveyor CI jobs finished running the tests successfully but they are marked as failures because of these tracebacks which appear when running the test suite |
|
OTOH, on Python 2, we don't see the font-related tracebacks but we do see the following traceback after all of the testsuites are run, which I guess is being interpreted as a failed job |
modified: appveyor.yml
|
@rahulporuri Thanks for picking this up, this is great! Do you have any spare cycles to investigate those two tracebacks further? |
I don't really know where the start. |
Hah, neither do I -- I was hoping you did :-) I've never seen the |
|
The second traceback is a WxPython issue caused by not properly disconnecting event handlers. If I recall, @RobinD42 fixed this in TraitsUI with this PR enthought/traitsui#108 . A similar fix may be needed in Enable? Both of these tracebacks are almost certainly Enable/Kiva problems not Chaco bugs. |
modified: appveyor.yml
modified: install-edm-windows.cmd
modified: install-edm-windows.cmd
|
@jvkersch I haven't been able to spend time investigating the tracebacks in the CI. Are you okay with merging this PR and opening issues to investigate the tracebacks? |
Sounds good! Merge away. |
|
merging now that the webhook for appveyor has been added |
The appveyor related additions made in this PR are based on the appveyor setup in traitsui.
Edit: closes #377