[
https://issues.apache.org/jira/browse/BEAM-6418?focusedWorklogId=197466&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-197466
]
ASF GitHub Bot logged work on BEAM-6418:
----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Feb/19 10:07
Start Date: 12/Feb/19 10:07
Worklog Time Spent: 10m
Work Description: mxm commented on issue #7510: [BEAM-6418] Execute Flink
tests serially to avoid memory issues
URL: https://github.com/apache/beam/pull/7510#issuecomment-462697426
I was asking myself the same question. I've tried lowering memory usage in
tests, but that did not fix it in all occasions. No other Runners execute three
different full-blown testing clusters at the same time. I've never had this
problem with parallel execution locally.
However, I've seen the "Exit Code 137" (killed by OS) also in other memory
intensive tests on Jenkins. I'm assuming at the moment it is not Flink
specific, but a very memory constraint test environment.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 197466)
Time Spent: 3.5h (was: 3h 20m)
> beam_PreCommit_Java_Cron failing
> --------------------------------
>
> Key: BEAM-6418
> URL: https://issues.apache.org/jira/browse/BEAM-6418
> Project: Beam
> Issue Type: Bug
> Components: runner-flink, test-failures
> Reporter: Ahmet Altay
> Assignee: Maximilian Michels
> Priority: Critical
> Fix For: Not applicable
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PreCommit_Java_Cron/814/console]
>
> *16:22:16* 1: Task failed with an exception.*16:22:16* -----------*16:22:16*
> * What went wrong:*16:22:16* Execution failed for task
> ':beam-runners-flink-1.6:test'.*16:22:16* > Process 'Gradle Test Executor
> 108' finished with non-zero exit value 137*16:22:16* This problem might be
> caused by incorrect test process configuration.*16:22:16* Please refer to
> the test execution section in the user guide at
> [https://docs.gradle.org/4.10.3/userguide/java_plugin.html#sec:test_execution]
> *16:22:16* *16:22:16* * Try:*16:22:16* Run with --stacktrace option to get
> the stack trace. Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.*16:22:16*
> ==============================================================================*16:22:16*
> *16:22:16* 2: Task failed with an exception.*16:22:16* -----------*16:22:16*
> * What went wrong:*16:22:16* Execution failed for task
> ':beam-runners-flink_2.11:test'.*16:22:16* > Process 'Gradle Test Executor
> 110' finished with non-zero exit value 1*16:22:16* This problem might be
> caused by incorrect test process configuration.*16:22:16* Please refer to
> the test execution section in the user guide at
> [https://docs.gradle.org/4.10.3/userguide/java_plugin.html#sec:test_execution]
> *16:22:16*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
