As I mentioned on the ticket I can reproduce the cpp errors regularly on my work machine if I can send info to folks lmk On Mar 15, 2013 2:32 AM, "Alexander Shraer" <shra...@gmail.com> wrote:
> Hello, > > I'm participating in the effort to track down the source of failures in > Zookeeper post-commit builds. > I can't reproduce the failures on nether Mac or Linux environments that I > have available so I'd like > to continue by trying to reproduce the failures on the build machine > asf008. Would it be possible for me to get access to > asf008 ? If possible, I'd like to be able to compile and run Zookeeper > test on that machine. > > Thanks, > Alex > > ---------- Forwarded message ---------- > From: Michi Mutsuzaki <mi...@cs.stanford.edu> > Date: Tue, Mar 12, 2013 at 11:15 AM > Subject: zookeeper build failure on as008.sp2.ygridcore.net > To: builds@apache.org > Cc: d...@zookeeper.apache.org > > > Hello, > > I'm debugging zookeeper build failure. The pre-commit build is passing > but the post-commit build is failing, so I'm guessing there might be > some difference in their build environments. The pre-commit build runs > on as009.sp2.ygridcore.net and the post-commit build runs on > asf008.sp2.ygridcore.net. Would it be possible for me to get access to > asf008 so that I can take a look at the build environment? If not, > could I get a copy of the build directory > (/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/)? > > https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1428/ > https://builds.apache.org/job/ZooKeeper-trunk/1860/ > > Thanks! > --Michi > >
