-
Notifications
You must be signed in to change notification settings - Fork 19
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
Test suite broken #61
Comments
What is causing this is that there is no good way of disabling all the tests that are known not to work. At least in my understanding. For all practical purposes, the test suite has always been broken for MATLAB. Sometimes changes to the module will cause some tests to fail more violently than before (e.g. crashing MATLAB), but that should not be a reason to hold back a commit. |
starting a git bisect |
The violently failing example appesrs to be dynamic_cast |
jaeandersson@jaeandersson-VirtualBox:~/dev/swig$ git bisect log bad: [98ed108] Merge branch 'dcb210-matlab' into matlabgit bisect bad 98ed108 good: [8e13c91] Revert "[MATLAB] issue #47: Fixes 'clear all' bug"git bisect good 8e13c91 good: [8f4101f] [MATLAB] issue #44: Enforced modulenameMATLAB_wrap naming convension for compiled mex functiongit bisect good 8f4101f bad: [b2aee0e] [MATLAB] issue #44: Removed unused variablesgit bisect bad b2aee0e bad: [f1a0155] [MATLAB] issue #44: Removed setup script functionality Usually not needed and when needed, any script can be called from the init functiongit bisect bad f1a0155 bad: [90e792f] [MATLAB] issue #44: Refactored initialization of modulesgit bisect bad 90e792f good: [72c5ccb] [MATLAB] issue #44: Added option for specifying mex-function infixgit bisect good 72c5ccb first bad commit: [90e792f] [MATLAB] issue #44: Refactored initialization of modules |
This is outdated, certainly after #96. I suggest to close this |
The test suite got (more) broken in one of the more recent commits.
The text was updated successfully, but these errors were encountered: