On 2013-10-29 10:03, Anders Logg wrote:
On Tue, Oct 29, 2013 at 10:30:03AM +0100, Johannes Ring wrote:
On Tue, Oct 29, 2013 at 10:06 AM, Martin Sandve Alnæs
<[email protected]> wrote:
> Some of the buildbots have been offline for a while.
I have restarted one (wheezy-amd64) and disabled the others now
(osx-10.6 and sid-amd64). The osx-10.6 buildbot machine has been
upgraded to OS X 10.8, but is currently not ready to be used as a
buildbot slave.
Great. I think we should only enable buildbots that are known to work.
> Some of them have strange timeouts.
sid-amd64 hang when compiling the fem convergence benchmark. I thought
this had been fixed when gcc 4.8.2 was uploaded to Debian unstable,
but it was not. Can someone else reproduce this timeout when compiling
this benchmark with gcc 4.8? We might want to disable building of this
benchmark.
It hangs for me with gcc 4.8.1. Does anyone know when a new gcc will
enter Ubuntu?
I wouldn't hold your breath - Ubuntu has a poor track record in
releasing bug fixes for development tools.
The benchmark builds fine if I disable P5 for R3. I suggest we disable
that benchmark for now and reenable it later. We should open an issue
so we don't forget it. (I can do this later today.)
> And at least two display this error:
>
> dolfin-master-full-precise-amd64
>
> [ 0%] Building CXX object
> test/unit/la/cpp/CMakeFiles/test_LinearOperator.dir/LinearOperator.cpp.o
> Linking CXX executable test_LinearOperator
> /home/buildbot/fenicsbbot/master/dolfin-full/lib/libdolfin.so: undefined
> reference to `METIS_Free'
That error was first encountered in this build:
http://fenicsproject.org:8010/builders/dolfin-master-full-precise-amd64/builds/417
Looks like Garth?
The correlation between code changes and buildbot errors has been very
weak of late. The error is a linking problem which is probably due to a
library configuration problem on the buildbot.
Garth
--
Anders
Johannes
> Martin
>
>
> On 29 October 2013 09:26, Anders Logg <[email protected]> wrote:
>>
>> When I look at the the DOLFIN buildbots, I see 5 red boxes for next
>> and 3 red boxes for master.
>>
>> That means the buildbot page cannot be used for checking the status
>> without clicking on each box and then making a judgement whether the
>> error was caused by a bug or by a missing library or a timeout.
>>
>>
>>
>> On Mon, Oct 28, 2013 at 10:52:19PM +0100, Martin Sandve Alnæs wrote:
>> > What do you mean by mixed state? As far as I can see they are mostly
>> > green
>> > except for some configuration related build errors and a couple of
>> > timeouts.
>> > Would of course be nice to have them all green.
>> >
>> > Martin
>> >
>> > mandag 28. oktober 2013 skrev Anders Logg følgende:
>> >
>> > What's the current status of the buildbots? They seem to be in a
>> > mixed
>> > state, both for next and master. I have stuff merged into next which
>> > hasn't been merged into master but don't know if I dare to merge it
>> > since both next and master seem to be broken.
>> >
>> > Can we get back to a default state where both next and master are
>> > always green?
>> >
>> >
>
> _______________________________________________
> fenics mailing list
> [email protected]
> http://fenicsproject.org/mailman/listinfo/fenics
>
_______________________________________________
fenics mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics
_______________________________________________
fenics mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics
