Oh, concurrent, there seems to be an errant geode build process making its way around the build boxes according to INFRA. S
On Tue, Jan 30, 2018 at 5:01 PM, Stack <st...@duboce.net> wrote: > Thanks Sean. Allen showed up on issues to report same. Trying to backfill > his recommendation on how to up proclimit count. > S > > On Tue, Jan 30, 2018 at 4:30 PM, Sean Busbey <bus...@apache.org> wrote: > >> This sounds like it could be caused by the new feature in yetus 0.7.0 to >> provide a configurable bound on resource usage, fyi. >> >> On Jan 30, 2018 08:53, "Stack" <st...@duboce.net> wrote: >> >> > Looking... >> > S >> > >> > On Tue, Jan 30, 2018 at 2:37 AM, 张铎(Duo Zhang) <palomino...@gmail.com> >> > wrote: >> > >> > > Seems like an infra issue. In the morning(in China) there is no >> available >> > > node under the label ubuntu... >> > > >> > > Anyone who can access the infra mailing list please send an email? I'm >> > not >> > > in that list yet... >> > > >> > > Thanks. >> > > >> > > 2018-01-30 18:11 GMT+08:00 Peter Somogyi <psomo...@cloudera.com>: >> > > >> > > > The Nightly build started to fail as well. >> > > > branch-2: https://builds.apache.org/job/ >> HBase%20Nightly/job/branch-2/ >> > > 223/ >> > > > artifact/output-jdk8-hadoop2/patch-unit-root.txt >> > > > >> > > > On Tue, Jan 30, 2018 at 11:01 AM, Peter Somogyi < >> psomo...@cloudera.com >> > > >> > > > wrote: >> > > > >> > > > > Hi, >> > > > > >> > > > > Recent precommit jobs are failing with OutOfMemoryError or >> "[ERROR] >> > > > unable >> > > > > to create new native thread". >> > > > > https://builds.apache.org/job/PreCommit-HBASE-Build/11250/ >> > > > > artifact/patchprocess/patch-mvninstall-root.txt >> > > > > <https://builds.apache.org/job/PreCommit-HBASE-Build/ >> > > > 11250/artifact/patchprocess/patch-mvninstall-root.txt> >> > > > > https://builds.apache.org/job/PreCommit-HBASE-Build/11251/ >> > > > > artifact/patchprocess/patch-unit-hbase-server.txt >> > > > > >> > > > > Can someone with access rights to Apache Jenkins take a look? >> > > > > >> > > > > Thanks, >> > > > > Peter >> > > > > >> > > > >> > > >> > >> > >
