There's a ton of jobs in the queue, maybe I can try on the weekend or when it is quieter if that's ok.
Thanks Szehon On Mon, Sep 14, 2015 at 1:55 PM, Pengcheng Xiong <pxi...@apache.org> wrote: > Thanks a lot Szehon! I saw "FATAL: Java heap space > java.lang.OutOfMemoryError > <http://stacktrace.jenkins-ci.org/search?query=java.lang.OutOfMemoryError > >: > Java heap space" > > May I ask if there is any way to increase the heap space? Or at least go > back to the previous settings because I remember It works even for 1000+ > failures before? > > Thanks again. > > Best > Pengcheng Xiong > > On Mon, Sep 14, 2015 at 1:38 PM, Szehon Ho <sze...@cloudera.com> wrote: > > > I meant, bottom of the Jenkins console output. > > > > On Mon, Sep 14, 2015 at 1:38 PM, Szehon Ho <sze...@cloudera.com> wrote: > > > > > I think the issue is at the bottom, seems like Java Heap Space when > > > Jenkins tries to upload the test report file :). It should work if > there > > > are a lesser set of failures. > > > > > > Thanks > > > Szehon > > > > > > On Mon, Sep 14, 2015 at 1:32 PM, Pengcheng Xiong <pxi...@apache.org> > > > wrote: > > > > > >> Hi folks, > > >> > > >> Did anyone of you notice that the pre-commit JIRA test output can > > not > > >> be seen in the browser if there are too many failures? For example, in > > my > > >> case I can not see > > >> > > >> > > >> > > > http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5265/testReport > > >> > > >> > > >> > > >> > > > http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5261/testReport > > >> > > >> However, if I remembered correctly, I can see them no matter how many > > >> failures there were before. > > >> > > >> Is it due to some recent changes on the infrastructure? Thanks. > > >> > > >> Best > > >> Pengcheng Xiong > > >> > > > > > > > > >
