ctest errors

Clearly defined bug reports and their fixes

ctest errors

Postby Gary R » 02 Aug 2017, 22:02

Since Debian Stretch (9?) has no binaries and Debian is woefully behind with Elmer, I decided to download the source code and compile locally. Cmake worked fine. Make worked fine. There were no errors in the whole compile and link sequence. When I ran ctest -V, I got over 500 errors, all for the same thing. The typical error message is as follows:

297: Elmergrid saving data with method 2:
297: -------------------------------------
297: Saving mesh in ElmerSolver format to directory Step_v2f.
297: Could not create a result directory!
297:
297: Thank you for using Elmergrid!
297: Send bug reports and feature wishes to elmeradm@csc.fi
297: -- BINARY_DIR = /home/gary/elmerfem
297: -- Extra library directories
297: CMake Error at /home/gary/elmerfem/cmake/Modules/test_macros.cmake:146 (FILE):
297: file failed to open for reading (No such file or directory):

297:
297: /home/gary/elmerfem/fem/tests/Step_v2f/TEST.PASSED
297: Call Stack (most recent call first):
297: runtest.cmake:2 (RUN_ELMER_TEST)
297:
297:
297/516 Test #297: Step_v2f ................................................***Failed

This would seem to be an error in the cmake system but am not sure.

Gary R.
Gary R
 
Posts: 60
Joined: 12 Apr 2012, 07:23
Location: Long Beach CA

Re: ctest errors

Postby mzenker » 03 Aug 2017, 19:10

Hi,

trivial question: could it be that the tests directory is write protected?

HTH,

Matthias
mzenker
 
Posts: 1695
Joined: 07 Dec 2009, 11:49
Location: Germany

Re: ctest errors

Postby Gary R » 03 Aug 2017, 21:25

Hi,
I did a chmod -R 777 * on the elmerfem directory. In short everything in the directory is writable. Still have the same problem.

Gary R
Gary R
 
Posts: 60
Joined: 12 Apr 2012, 07:23
Location: Long Beach CA

Re: ctest errors

Postby Gary R » 04 Aug 2017, 05:17

All of a sudden the errors dropped from 516 to 6. They are:

133 - ElasticBeamRestart (Failed)
177 - InternalPartitioning_np8 (Failed)
179 - InternalPartitioning2_np6 (Failed)
181 - InternalPartitioning3_np6 (Failed)
376 - circuits_harmonic_stranded_homogenization (Failed)
450 - mgdyn_harmonic_wire (Failed)

All of the above errored in exactly the same way. See 133 below.

133: Thank you for using Elmergrid!
133: Send bug reports and feature wishes to elmeradm@csc.fi
133: ELMER SOLVER (v 8.3) STARTED AT: 2017/08/03 19:08:00
133: ParCommInit: Initialize #PEs: 1
133: MAIN:
133: MAIN: =============================================================
133: MAIN: ElmerSolver finite element software, Welcome!
133: MAIN: This program is free software licensed under (L)GPL
133: MAIN: Copyright 1st April 1995 - , CSC - IT Center for Science Ltd.
133: MAIN: Webpage http://www.csc.fi/elmer, Email elmeradm@csc.fi
133: MAIN: Version: 8.3 (Rev: de6b3bad, Compiled: 2017-07-31)
133: MAIN: =============================================================
133: ERROR:: InitializeElementDescriptions: elements.def not found
133: -- BINARY_DIR = /home/gary/elmerfem
133: -- Extra library directories
133: CMake Error at /home/gary/elmerfem/cmake/Modules/test_macros.cmake:146 (FILE):
133: file failed to open for reading (No such file or directory):

Gary R
Gary R
 
Posts: 60
Joined: 12 Apr 2012, 07:23
Location: Long Beach CA

Re: ctest errors

Postby mzenker » 04 Aug 2017, 09:30

Well, I would say that your Elmer installation principally works, since almost all tests succeeded. Why it doesn't find the elements.def I don't know. Is there a file of that name in share/elmersolver/lib in the Elmer installation directory?
If so, one would have to examine those tests closer.

HTH,
Matthias
mzenker
 
Posts: 1695
Joined: 07 Dec 2009, 11:49
Location: Germany

Re: ctest errors

Postby Gary R » 05 Aug 2017, 04:14

Update,
I found a source that listed several other packages that needed to be installed if you wished to get the most out of Elmer. I installed the packages, reran make with -B switch and am now down to two errors running ctest. The recommended packages were qt4-dev-tools, qt4-default (if debian), libqwt-qt5-6, vtk6 and liboce-ocaf10. It seems that there should be some sort of preliminary system check that would list missing and/or suggested software.

The two errors are:
376 - circuits_harmonic_stranded_homogenization (Failed)
450 - mgdyn_harmonic_wire (Failed)
Again, both have the same error message:

450:
450: Thank you for using Elmergrid!
450: Send bug reports and feature wishes to elmeradm@csc.fi
450: -- BINARY_DIR = /home/gary/elmerfem
450: -- Extra library directories
450: CMake Error at /home/gary/elmerfem/cmake/Modules/test_macros.cmake:149 (MESSAGE):
450: Test failed
450: Call Stack (most recent call first):
450: runtest.cmake:2 (RUN_ELMER_TEST)
450:
450:
2/2 Test #450: mgdyn_harmonic_wire .........................***Failed 7.18 sec

Which isn't much help. Line 149 just indicates that there was a test error.

Any incites will be sincerely appreciated.

Gary R
Gary R
 
Posts: 60
Joined: 12 Apr 2012, 07:23
Location: Long Beach CA

Re: ctest errors

Postby mzenker » 06 Aug 2017, 14:33

Hi,

as was said in other posts at this forum, a few failed tests are usually not that problematic. You can try to run the tests by hand if you really want to track down the problem. If you examine the test directory, you usually find out quite easily what the commands are to be run off the command line - generally one call to ElmerGrid and one to ElmerSolver, with appropriate arguments.
Otherwise people more experienced in that matter have to take over...

Matthias
mzenker
 
Posts: 1695
Joined: 07 Dec 2009, 11:49
Location: Germany


Return to Bug reports

Who is online

Users browsing this forum: No registered users and 2 guests