Hi ! First of all, congratulation for this great piece of software !
I was trying to build and install SfePy system-wide (2014.1 or 2014.2), but ran into troubles. I followed the instructions on the website ("python setup.py build", then "python setup.py install"). There was no special error during the build (some warnings from gcc) or the installation.
However, when I try to run the tests, nothing is working :
79 test file(s) executed in 0.55 s, 92 failure(s) of 103 test(s)
The errors are due to python that fails to import SfePy modules :
./run_tests.py --debug tests/test_cmesh.py
.... .... .... File "tests/test_cmesh.py", line 96, in test_cmesh_counts from sfepy.discrete.fem import Mesh File "/scratch/packages/sfepy-2014.2/sfepy/discrete/__init__.py", line 8, in <module> from variables import Variables, Variable, FieldVariable, create_adof_conns File "/scratch/packages/sfepy-2014.2/sfepy/discrete/variables.py", line 12, in <module> import sfepy.linalg as la File "/scratch/packages/sfepy-2014.2/sfepy/linalg/__init__.py", line 1, in <module> from extmods.crcm import rcm, permute_in_place ImportError: No module named crcm
I don't understant, because everything is installed in my /usr/local/lib/python2.7/ (I run an ubuntu 14.04)
If I do an inplace build, everything works fine (but I really want to install SfePy system-wide...)
I really don't know how to fix that... any idea ?
Thank you very much ! G.
Hi!
On 06/11/2014 02:11 PM, G.L. wrote:
Hi ! First of all, congratulation for this great piece of software !
Thank you.
I was trying to build and install SfePy system-wide (2014.1 or 2014.2), but ran into troubles. I followed the instructions on the website ("python setup.py build", then "python setup.py install"). There was no special error during the build (some warnings from gcc) or the installation.
However, when I try to run the tests, nothing is working :
79 test file(s) executed in 0.55 s, 92 failure(s) of 103 test(s)
Do you run the tests as below? "./run_tests.py" implies that you are in the sfepy directory.
The errors are due to python that fails to import SfePy modules :
./run_tests.py --debug tests/test_cmesh.py
.... .... .... File "tests/test_cmesh.py", line 96, in test_cmesh_counts from sfepy.discrete.fem import Mesh File "/scratch/packages/sfepy-2014.2/sfepy/discrete/__init__.py", line 8, in <module> from variables import Variables, Variable, FieldVariable, create_adof_conns File "/scratch/packages/sfepy-2014.2/sfepy/discrete/variables.py", line 12, in <module> import sfepy.linalg as la File "/scratch/packages/sfepy-2014.2/sfepy/linalg/__init__.py", line 1, in <module> from extmods.crcm import rcm, permute_in_place ImportError: No module named crcm
I don't understant, because everything is installed in my /usr/local/lib/python2.7/ (I run an ubuntu 14.04)
If I do an inplace build, everything works fine (but I really want to install SfePy system-wide...)
I really don't know how to fix that... any idea ?
It seems that you are running the tests in the sfepy directory, without building the modules in place. Try cd somewhere else...
Cheers, r.
Le mercredi 11 juin 2014 14:45:09 UTC+2, Robert Cimrman a écrit :
It seems that you are running the tests in the sfepy directory, without building the modules in place. Try cd somewhere else...
Cheers, r.
I am a total looser, thank you very much for the hint... I tried again and again to make the the ./run_test work without testing any example by hand...
Best regards, G.
On 06/12/2014 05:47 PM, G.L. wrote:
Le mercredi 11 juin 2014 14:45:09 UTC+2, Robert Cimrman a écrit :
It seems that you are running the tests in the sfepy directory, without building the modules in place. Try cd somewhere else...
Cheers, r.
I am a total looser, thank you very much for the hint... I tried again and again to make the the ./run_test work without testing any example by hand...
Best regards, G.
It is a tricky thing :)
hth, r.
Am Donnerstag, 12. Juni 2014 19:24:37 UTC+2 schrieb Robert Cimrman:
On 06/12/2014 05:47 PM, G.L. wrote:
Le mercredi 11 juin 2014 14:45:09 UTC+2, Robert Cimrman a écrit :
It seems that you are running the tests in the sfepy directory, without building the modules in place. Try cd somewhere else...
Cheers, r.
I am a total looser, thank you very much for the hint... I tried again
and
again to make the the ./run_test work without testing any example by hand...
Best regards, G.
It is a tricky thing :)
hth, r.
Just a short comment: I had the same problem and it turned out that I misunderstood the installation instructions. I thought one has to choose among in-place use and installation. Maybe it would be useful to adopt the instructions by adding a comment that running the in-place build is needed in both cases.
kind regards Josip
On 10/21/2014 09:34 PM, mihaljev...@googlemail.com wrote:
Am Donnerstag, 12. Juni 2014 19:24:37 UTC+2 schrieb Robert Cimrman:
On 06/12/2014 05:47 PM, G.L. wrote:
Le mercredi 11 juin 2014 14:45:09 UTC+2, Robert Cimrman a écrit :
It seems that you are running the tests in the sfepy directory, without building the modules in place. Try cd somewhere else...
Cheers, r.
I am a total looser, thank you very much for the hint... I tried again
and
again to make the the ./run_test work without testing any example by hand...
Best regards, G.
It is a tricky thing :)
hth, r.
Just a short comment: I had the same problem and it turned out that I misunderstood the installation instructions. I thought one has to choose among in-place use and installation. Maybe it would be useful to adopt the instructions by adding a comment that running the in-place build is needed in both cases.
kind regards Josip
Thanks for pointing that out - I never noticed that the testing instructions correspond only to the in-place build without mentioning how to test when the code is installed (i.e. run run_tests.py from a different directory than the source directory). Could you create an issue for that? (Or a pull request - contributions welcome!)
r.
On 10/21/2014 10:45 PM, Robert Cimrman wrote:
On 10/21/2014 09:34 PM, mihaljev...@googlemail.com wrote:
Just a short comment: I had the same problem and it turned out that I misunderstood the installation instructions. I thought one has to choose among in-place use and installation. Maybe it would be useful to adopt the instructions by adding a comment that running the in-place build is needed in both cases.
kind regards Josip
Thanks for pointing that out - I never noticed that the testing instructions correspond only to the in-place build without mentioning how to test when the code is installed (i.e. run run_tests.py from a different directory than the source directory). Could you create an issue for that? (Or a pull request - contributions welcome!)
I have improved the installation instructions. Feedback welcome!
r.
participants (3)
-
G.L. -
mihaljev...＠googlemail.com -
Robert Cimrman