Make test failures on master branch

When I run “make test” I get the following failures:

The following tests FAILED:
5 - gr-core-test-all (Failed)
23 - qa_hier_block2 (Failed)
70 - qa_vector_sink_source (Failed)

The …/build/Testing/Temporary/LastTest.log file is attached.

I’m particularly concerned about the failure with gr-core, but the log
output doesn’t mean much to me. Should I be concerned about these
failures? If so, what can I do?

I’ve tried on two different master branch commits and had the same
failures:
$ git show
commit 99ebcc1c3ff453ea10e934ef1904b42821d589f1
Merge: c662d1c a69f262
Author: Johnathan C. [email protected]
Date: Thu Apr 5 11:47:01 2012 -0700

Merge remote branch 'ncorgan/gr-uhd_swig'

$ git show
commit fc6151d4516ee86b697602014b83fb08a88c30f0
Merge: 89f934b fa161e1
Author: Tom R. [email protected]
Date: Sun Dec 11 23:01:34 2011 -0500

Merge remote-tracking branch 'jblum/cmake_qtgui_fix'

I’m on RHEL 5 x86_64:
$ cat /proc/version

Linux version 2.6.18-274.3.1.el5
([email protected]) (gcc version 4.1.2 20080704 (Red
Hat
4.1.2-51)) #1 SMP Fri Aug 26 18:49:02 EDT 2011

$ lsb_release -i -r

Distributor ID: RedHatEnterpriseClient

Release: 5.7

Thanks for any insight.
Justin

On 04/05/2012 04:04 PM, Justin F. wrote:

When I run “make test” I get the following failures:

The following tests FAILED:
5 - gr-core-test-all (Failed)
23 - qa_hier_block2 (Failed)
70 - qa_vector_sink_source (Failed)

The unit tests arent always so telling. You can dig down into the tests
with the xml file they produce. I think its goes in your home dir like
so: cat ~/.gnuradio/unittests/python/test_hier_block2.xml

Can you attach the xml files, it might be helpful to narrow down the
failure.

-josh

On Fri, Apr 6, 2012 at 10:36 AM, Justin F. [email protected]
wrote:

This is free software; see the source for copying conditions. There is NO
installed along side the old versions built into RHEL:
$ cmake -DPYTHON_EXECUTABLE=/usr/bin/python26
-DBOOST_INCLUDEDIR=/usr/include/boost141
-DBOOST_LIBRARYDIR=/usr/lib64/boost141
-DSWIG_EXECUTABLE=/usr/share/swig/2.0.4/bin/swig …/

Are there other important platform specifics that I haven’t mentioned?

Justin

Just noticed I had dropped the mailing list off my replies…

Absolutely. I’m also concerned I have some underlying platform issue.

Thanks for working with me, Josh. Today I gave up and went to RHEL 6.
The build went fine. Hopefully the rest of what I indend to do will
work well on this “new” OS. Should have probable started here…too
many out of date dependencies on RHEL 5.

$ cat /proc/version
Linux version 2.6.32-220.el6.x86_64
([email protected]) (gcc version 4.4.5 20110214
(Red Hat 4.4.5-6) (GCC) ) #1 SMP Wed Nov 9 08:03:13 EST 2011

$ cat /etc/redhat-release
Red Hat Enterprise Linux Workstation release 6.2 (Santiago)

$ git show
commit 779d8c67ae520ab76198019e656c86c88281719d
Merge: 3de14a2 c7139a7
Author: Johnathan C. [email protected]
Date: Mon Apr 9 14:10:26 2012 -0700

$ make test

100% tests passed, 0 tests failed out of 101

In case it helps someone, these packages from RHEL and EPEL will cover
the dependencies for UHD and GR (listed by yum package name):
boost*
cmake
cppunit*
fftw
fftw-devel
fftw-static
git-all
gsl*
guile*
libusb*
orc*
pcre*
python-docutils
pygtk*
PyQt4*
PyQwt*
pyxdg
qt*
qwt*
sdcc*
wxPython*
xdg-utils

With those in place, both the UHD and GR latest master git branches
built today.

Justin