On most (but not all) dartclients mitkNavigationToolReaderAndWriterTest fails with following messsage "core.mod.scnSer.scnIo ERROR: Could not create ZIP file..."
Until this is solved I will deactivate the test to have a better overview on the dashboard changes.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | None | T3343 memcheck errors in mitkNavigationToolReaderAndWriterTest | ||
| Resolved | None | T3461 mitkNavigationToolReaderAndWriterTest fails | ||
| Resolved | None | T3336 mitkSceneIOTest fails randomly |
The error is caused by the class mitk::SceneIO, which is used in the classes mitkNavigationToolReader and mitkNavigationToolWriter. So this bug is related to T3336, where the same error is described for the class mitk::SceneIO.
By the way, the bug is perhaps caused by the creation of the temp directory (line 54, method CreateEmptyTempDirectory()). I assume that some of the dart clients may not have write access to this directory. Perhaps the bug would be solved by using the method mitk::StandardFileLocations::GetInstance()->GetOptionDirectory() for getting a temp directory instead of the poco-method.
@Daniel: would you please reactivate this test as soon as your bug no 3336 is solved?
(example error message: core.mod.scnSer.scnIo ERROR: Could not create ZIP file from C:\DOKUME~1\schwarzt\LOKALE~1\Temp\tmp3656aaaaaa)
(In reply to comment #2)
The error is caused by the class mitk::SceneIO, which is used in the classes
mitkNavigationToolReader and mitkNavigationToolWriter. So this bug is related
to T3336, where the same error is described for the class mitk::SceneIO.By the way, the bug is perhaps caused by the creation of the temp directory
(line 54, method CreateEmptyTempDirectory()). I assume that some of the dart
clients may not have write access to this directory. Perhaps the bug would be
solved by using the method
mitk::StandardFileLocations::GetInstance()->GetOptionDirectory() for getting a
temp directory instead of the poco-method.@Daniel: would you please reactivate this test as soon as your bug no 3336 is
solved?
If I should fix T3336, yes, I'll think of reactivating your test. However, I'm not very active in bug fixing at the moment. If you want you can continue to investigate the problem. Feel free to make changes in SceneIO, too. MITK follows the concept of "collective code ownership".