*huh* .. in the case of an OutOfMemory I suppose all bets are off? The machine that would be used to build your project is unable to spawn the maven process. Sounds like something that should be filed as a INFRA ticket.
2017-08-01 16:24 GMT+02:00 Maxim Solodovnik <solomax...@gmail.com>: > Lots of build fails with: > > Error occurred during initialization of VM > java.lang.OutOfMemoryError: unable to create new native thread > ERROR: Failed to launch Maven. Exit code = 1 > > > and no emails are being sent :( > > On Tue, Aug 1, 2017 at 12:44 PM, Maxim Solodovnik <solomax...@gmail.com> > wrote: > > > Another example of failed build: https://builds.apache.org/ > view/M-R/view/ > > OpenMeetings/job/openmeetings/1737 > > > > On Tue, Aug 1, 2017 at 12:26 PM, Maxim Solodovnik <solomax...@gmail.com> > > wrote: > > > >> Hello, > >> > >> Somehow I'm not receiving emails about failed/unstable builds anymore > >> Configuration [1] unstable build [2] > >> Can it be fixed? Or maybe there is something wrong with configuration? > >> > >> [1] https://builds.apache.org/view/M-R/view/OpenMeetings/job > >> /Openmeetings%203.3.x/configure > >> [2] https://builds.apache.org/view/M-R/view/OpenMeetings/job > >> /Openmeetings%203.3.x/100/ > >> > >> -- > >> WBR > >> Maxim aka solomax > >> > > > > > > > > -- > > WBR > > Maxim aka solomax > > > > > > -- > WBR > Maxim aka solomax > -- Dominik Psenner
