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.
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. On Sun, Nov 9, 2014 at 12:45 PM, Erik Schnetter <[email protected]> wrote: > I see that the ET build server is failing for the past two commits. I > can only access the commit messages on the build server's web pages, > and they point to unrelated Simfactory MDB changes. Is there a way to > get a complete diff between the last succeeding and the first failing > version? > > The error message points to PETSc and how it configures MPI. > > -erik > > -- > Erik Schnetter <[email protected]> > http://www.perimeterinstitute.ca/personal/eschnetter/ > _______________________________________________ > Users mailing list > [email protected] > http://lists.einsteintoolkit.org/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.einsteintoolkit.org/mailman/listinfo/users
