failed to import hit - try running "make hit" in the $MOOSE_DIR/test directory.

[dealm...@gmail.com]

Hello,
I have compiled MOOSE twice today and I am getting stuck at the testing phase:

cd ~/projects/moose/test
make -j8
./run_tests -j8

->  ./run_tests -j8
failed to import hit - try running "make hit" in the $MOOSE_DIR/test directory.

I have issued the "make hit" command but it does not help.
There is no apparent sign of something have gone bad during the long compilation of libmesh.
Is there a particular place to look for build errors?

Thanks,
--
Valmor

[dealm...@gmail.com]

This problem is solved having python 2.7 as my primary python interpreter (I typically use python 3.5).
Maybe a warning on run_tests about the python version used could be helpful.
--
Valmor

[princessandsuperman]

The test harness (i.e. run_tests script) uses a C python extension for parsing MOOSE input files that is compiled against whatever python-install is reported by "python-config --prefix".  We recently changed our run_tests script bang line to read "python2" instead of "python" (since we require python 2).  But we never changed the build system to use python2-config when building the input file parser python bindings.  So if python and python2 don't point to the same python, you will see this problem.  I created an issue (https://github.com/idaholab/moose/issues/11556)

[Mohamed Ezzat Mostafa]

Hey--

I faced the same pronblem when I am installing one of moose application called (Zapdos). I installed it three weeks ago and it passed but I trying to re organize my PC and hence I removed moose and zapdos (just removed the projects directory where both are located) to re intall everything again.  MOOSE installtion passed while Zapdos report me this error: failed to import hit - try running "make hit" in the $MOOSE_DIR/test directory.
FYI: python and python2 refer to the python2 while python3 refer to python3. 

Looking for any soultion

Thanks in advance

Mohamed

---------------------------

[Jason Miller]

Can you copy/paste exactly where you go (cd), and what you are executing? Also, the results of an `env` might help --I'm heading in the general direction that it is possible you have a MOOSE_DIR set, and pointing to projects/moose (which you have moved/removed), and thus, no more hit parser at that location.

Thanks!

Jason

--
You received this message because you are subscribed to the Google Groups "moose-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moose-users...@googlegroups.com.
Visit this group at https://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/f55e18b9-f168-4363-a728-23223b0fc126%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.