Quantcast

buildbot test failures

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

buildbot test failures

John W. Eaton
Administrator
I recently made some changes so that buildbot builds report success only
if the number of failed tests is exactly 0.  You can see here

   buildbot.octave.org:8010

that we currently aren't doing so well.

On the system that runs the following builders

   gcc-fedora
   gcc-lto-fedora
   clang-fedora

some tests fail because of a current fedora bug in osmesa.  I suppose I
could (temporarily) disable osmesa on those systems to eliminate the
failures.

On the system that runs the following builders

   gcc-6-debian
   clang-3.9-debian

8 tests are failing because there is no audio device.  I could skip
those tests if there were a way to check whether audio devices are
available, but I'm not sure how to do that.  Currently, audiodevinfo
throws an error if there is no audio device.  Would it be OK to change
that so it simply returns an empty structure?  For my purposes that
would make checking easier, but I'm not sure whether it will cause other
trouble.

The clang-osx build fails because of a problem with integer typedefs
that I reported here:

   https://savannah.gnu.org/bugs/?50510

The gcc-6-lto-debian build fails because of a mysterious problem saving
and loading signed 32-bit integers to HDF5 files.

And finally, the mxe-native-on-debian build is failing because the
of-database package configure script is failing with the following message:

   checking for PQconnectdb in -lpq... no
   configure: error: unable to find the PQconnectdb() function in pq

but I think that's just a missing package problem on my build system, so
I'll fix that and try again.

I'd like to eliminate these failures in some way so that we can expect
to see all builds regularly succeeding.  If failures are rare, then I
think we can be more sure that regressions are noticed soon after they
happen.

Comments, suggestions, and help are all welcome.

Thanks,

jwe


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: buildbot test failures

Olaf Till-2
On Wed, Mar 15, 2017 at 05:06:34PM -0400, John W. Eaton wrote:
> And finally, the mxe-native-on-debian build is failing because the
> of-database package configure script is failing with the following message:
>
>   checking for PQconnectdb in -lpq... no
>   configure: error: unable to find the PQconnectdb() function in pq

At this point the pg_config binary should already have been found, so
it seems you have postgresql installed. Postgresql normally comes with
libpq...

Olaf

> but I think that's just a missing package problem on my build system, so
> I'll fix that and try again.

--
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: buildbot test failures

John W. Eaton
Administrator
On 03/16/2017 02:02 AM, Olaf Till wrote:

> On Wed, Mar 15, 2017 at 05:06:34PM -0400, John W. Eaton wrote:
>> And finally, the mxe-native-on-debian build is failing because the
>> of-database package configure script is failing with the following message:
>>
>>   checking for PQconnectdb in -lpq... no
>>   configure: error: unable to find the PQconnectdb() function in pq
>
> At this point the pg_config binary should already have been found, so
> it seems you have postgresql installed. Postgresql normally comes with
> libpq...
>
> Olaf
>
>> but I think that's just a missing package problem on my build system, so
>> I'll fix that and try again.

Oh, I just realized that since this is an mxe-octave build, it's not a
missing dependency problem that should be solved by installing something
on the build system, but it's something that should be fixed in
mxe-octave or the package configure script.

I see that the postgresql package has been installed by mxe-octave and
that the database package configure script finds pg_config.  But the
-lpq library is not found, even though it is installed (in the
mxe-octave usr/lib directory.  The config.log file says

configure:3340: checking for PQconnectdb in -lpq
configure:3365: gcc -o conftest -g -O2   conftest.c -lpq   >&5
/usr/bin/ld: cannot find -lpq
collect2: error: ld returned 1 exit status

This build is using the system compiler which doesn't search the
mxe-octave directories by default.  So compiler flags like CPPFLAGS,
CFLAGS, CXXFLAGS, FFLAGS, and LDFLAGS should really be set so that
libraries compiled and installed by mxe-octave should be found instead
of the ones installed in system directories.

I think it should be working for the next build that is attempted
because I installed the libpq-dev package on that buildbot worker
system, but that's not really the right fix.

To properly test this kind of build, I think we need to do it in a VM or
on some other system that has a minimal set of development dependencies
installed.  I don't think it's anything that you need to fix in the
database package.

jwe


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: buildbot test failures

Carnë Draug
In reply to this post by John W. Eaton
On 15 March 2017 at 21:06, John W. Eaton <[hidden email]> wrote:
> [...]
> 8 tests are failing because there is no audio device.  I could skip those
> tests if there were a way to check whether audio devices are available, but
> I'm not sure how to do that.  Currently, audiodevinfo throws an error if
> there is no audio device.  Would it be OK to change that so it simply
> returns an empty structure?  For my purposes that would make checking
> easier, but I'm not sure whether it will cause other trouble.
> [...]

Returning an empty struct makes sense to me.  However, audiodevinfo is
a Matlab function so I guess we should do whatever Matlab does.

I tried to test it (in Matlab R2010b) but got an error back saying
that it only works on Windows.

Carnë

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: buildbot test failures

Olaf Till-2
In reply to this post by John W. Eaton
On Thu, Mar 16, 2017 at 10:37:04AM -0400, John W. Eaton wrote:
> To properly test this kind of build, I think we need to do it in a VM or on
> some other system that has a minimal set of development dependencies
> installed.  I don't think it's anything that you need to fix in the database
> package.

Ok. But if you should use the released version of the package, I'd
recommend using latest tip. Otherwise you may run into a bug in the
Makefile which probably affects cross building (-L option for pq set
_before_ -L options for Octave libs in the g++ commandline). If
necessary, I can make a new release.

Olaf

--
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

signature.asc (836 bytes) Download Attachment
Loading...