Hi mesos-devs, Ben and I added another Jenkins build job tonight that, like the other 2 jobs, checks out the code after each commit (e.g. they are all running right now since we just committed Charles patch for MESOS-81). Then, unlike the other tests, this new one (#1 in the list below) tries to build in the src directory.
We now have three tests that run, with the following names: 1. Mesos-Trunk-Ubuntu-Build-In-Src 2. Mesos-Trunk-Ubuntu-Build-Out-Of-Src 3. Mesos-Trunk-Ubuntu-Configure-Without-Options We expect (3) to fail currently, this should go away once we move to Automake, which we are hoping to get done in the next week. Andy On Tue, Nov 15, 2011 at 10:33 PM, Apache Jenkins Server < [email protected]> wrote: > See <https://builds.apache.org/job/Mesos-Trunk-Ubuntu-Build-In-Src/2/> > > ------------------------------------------ > Started by an SCM change > Building remotely on ubuntu2 > Updating https://svn.apache.org/repos/asf/incubator/mesos/trunk > At revision 1202544 > no change for https://svn.apache.org/repos/asf/incubator/mesos/trunksince the > previous build > [Mesos-Trunk-Ubuntu-Build-In-Src] $ /bin/bash -xe > /tmp/hudson7214995038412327585.sh > + export JAVA_HOME=/home/jenkins/tools/java/jdk1.6.0_20-64 > + JAVA_HOME=/home/jenkins/tools/java/jdk1.6.0_20-64 > + export > PATH=/home/jenkins/tools/java/jdk1.6.0_20-64/bin:/home/hudson/tools/java/latest1.6/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/home/hudson/.rvm/bin > + > PATH=/home/jenkins/tools/java/jdk1.6.0_20-64/bin:/home/hudson/tools/java/latest1.6/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/home/hudson/.rvm/bin > + ../configure --with-python-headers=/usr/include/python2.6 --with-webui > --with-java-home=/home/jenkins/tools/java/jdk1.6.0_20-64 > --with-java-headers=/home/jenkins/tools/java/jdk1.6.0_20-64/include > --with-included-zookeeper > /tmp/hudson7214995038412327585.sh: line 8: ../configure: No such file or > directory > Build step 'Execute shell' marked build as failure > >
