On 10 Nov 2014, at 08:26, Roland Haas <[email protected]> wrote:
> Hello all, > >> The commit message lists all new commits to ET repositories in each build, >> so I think those are indeed the only changes to the ET code between >> revisions. The error is most likely unrelated to the changes in the >> commits. The last successful build (#322) was done on the CCT build slave, >> as were all of the previous successful builds I checked. The two most >> recent builds, however, were done on the Caltech slave (since the CCT >> machine is temporarily offline) and both of those failed. So I guess there >> must be some problem with the Caltech build slave. > The Caltech slave will currently always fail since it was updated to > Ubuntu 14.04 but the simfactory option list that the build system uses > does not work with this version of Ubuntu (since the mpich include files > moved). I can switch back the slave to the "old" Ubuntu version (there's > a snapshot of the virtual machine for this reason). I cannot I think > update the option list used in simfactory. Hi Roland, The optionlist used by the build and test system is in https://bitbucket.org/ianhinder/cactusjenkins/src/ (called build.cfg) and you now have commit access. The change appears to be backward-compatible; please feel free to commit it if this is the case. >> I have now temporarily disabled the Caltech build slave until someone can >> fix the problem. Builds will now happen on the Perimeter slave, assuming >> that is functioning correctly. > Thank you. Sorry, I didn't realise that this had happened. The build nodes are all supposed to be identical; if we update one of them for testing, it should be taken out of the pool. Once the testing node is working, we should update the other nodes as well. -- Ian Hinder http://numrel.aei.mpg.de/people/hinder
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Users mailing list [email protected] http://lists.einsteintoolkit.org/mailman/listinfo/users
