-
Notifications
You must be signed in to change notification settings - Fork 0
test have to be run from a specific directory #25
Comments
see bugs simphony/simphony-common#148 and simphony/simphony-common#144 for specific bugs regarding the H5Mesh objects that can lead to corrupted data |
Corrected description and title, the problems is still there but it is caused not been in the root folder of the repo when running |
In the current working branch (fix-issues-july2015), we are proposing a dynamic discovery of the mesh file during the test run. It requires adds the 'simplemesh.cuds' to the installation, and look it in the 'site_packages' folder. With this change, the unittest is working from any folder. As @itziakos said, It is better not to depend on a file but create the CUDS containers components at runtime. But, to do that, we must wait for stabilizing of the hdf5 version. |
If the tests create the containers on the fly at runtime there is no need for using the hdf5 backend and thus no reason to wait. |
Note: We have returned back with this change. The issue is still open. |
@khiltunen , i think this can be closed as you fixed it in #53, right? |
You are right |
closed by #53 |
Running the test suite
python -m unittest discover foam_controlwrapper from any directory except the repo folder fails with the following errors.
It looks that the test case is a little fagile and expects that the 'simplemesh.cuds' is also installed at a specific directory and that the test runner started from a specific working directory.
One needs to probably adds the 'simplemesh.cuds' to the installation and dynamically discover it during the test run, but this is a temporary solution. It is better not to depend on a file but create the CUDS containers components at runtime. It is also frigile since the cuds hdf5 layout is provisional and so future versions of
simphony-common
are not expected to be backwards compatible until we stabilise the hdf5 layout and setup a layout versioning.The text was updated successfully, but these errors were encountered: