[
https://issues.apache.org/jira/browse/BEAM-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726035#comment-16726035
]
Robert Burke commented on BEAM-6281:
------------------------------------
I agree. It looks like the machine got too busy and then the program died
trying to get more memory. I'd say it was during garbage collection somehow,
but that seems unlikely.
I don't know enough about the Jenkin's set up to understand why that happened
at this time, but there hasn't been any changes along Go code that could have
caused that in the last day or so.
> Jenkins failure in Go SDK PostCommit
> ------------------------------------
>
> Key: BEAM-6281
> URL: https://issues.apache.org/jira/browse/BEAM-6281
> Project: Beam
> Issue Type: Bug
> Components: build-system, sdk-go, test-failures
> Reporter: Kenneth Knowles
> Assignee: Robert Burke
> Priority: Critical
>
> https://builds.apache.org/job/beam_PostCommit_Go/2047/console
> {code}
> *08:43:58* runtime/cgo: pthread_create failed: No space left on device
> *08:43:58* SIGABRT: abort*08:43:58* PC=0x7faf428f9428 m=3
> sigcode=18446744073709551610
> {code}
> This looks like the Jenkins worker just beefed - but will you peek at the log
> with your Go-knowing eyes and see if there's anything about the run that
> could be our fault / we could change to make it not happen?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
