Tests broken by recent Python updates

Development
1

Something in the changes between 25945 and 25971 seems to have broken a number of Python tests in extensions, e.g.:

http://slicer.cdash.org/index.php?project=Slicer4&date=2017-04-25&filtercount=1&showfilters=1&field1=label&compare1=63&value1=Chest

http://slicer.cdash.org/index.php?project=Slicer4&date=2017-04-26&filtercount=1&showfilters=1&field1=label&compare1=63&value1=Chest

(also SlicerDMRI and others)

2

Before rev 25970, many Python tests were actually not executed. Now they are, so you can expect test errors to show up. You have to review and fix those tests.

Details: There was a problem in CTK argument parser that made all parameters after --additional-module-paths argument ignored (all further arguments were interpreted as additional paths). All python tests that relied on running a python script using --python-script actually did not test anything, just started Slicer and quit.

1 Like