Difference between revisions of "Developer Meetings/20130212"

Revision as of 20:28, 12 February 2013

ITKv4 enabled by default / SimpleITK updated to v0.6.1. See r21688
- Review list of existing issue (mantis tag: ITKv4)
Approach to display log on windows: http://slicer-devel.65872.n3.nabble.com/Windows-command-line-tp4027441p4027524.html
- Log to file ?
- Provide an other (application + Launcher) which would be console aware ?
Demo AutoRun for CLI modules (Julien, #2940)
Continuous integration
- Test takes way too long - What about creating a ctest LABEL named "fast" or one named "slow". It would then be easy to run integration tests: ctest -L fast or ctest -LE slow
- Python self test are very long. Does it make sens to run them continously. What about one time a week ? During the weekend ?
Refactor of Python self test
- Duplicated code :( ... => maintenance hell. See third point reported here.
Re-enable setup windows 32-bit nightly

@@ Line 8: / Line 8: @@
 * Continuous integration
 ** Test takes way too long - What about creating a ctest LABEL named "fast" or one named "slow". It would then be easy to run integration tests: <code>ctest -L fast</code> or <code>ctest -LE slow</code>
+** Python self test are very long. Does it make sens to run them continously. What about one time a week ? During the weekend ?
+* Refactor of Python self test
+** Duplicated code :( ... => maintenance hell. See third point reported [http://www.na-mic.org/Wiki/index.php/2013_Project_Week:SelfTests here].
 * Re-enable setup windows 32-bit nightly
 == Conclusion ==