You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/14 02:55:00 UTC
[jira] [Work logged] (BEAM-6418) beam_PreCommit_Java_Cron failing
[ https://issues.apache.org/jira/browse/BEAM-6418?focusedWorklogId=184662&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-184662 ]
ASF GitHub Bot logged work on BEAM-6418:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jan/19 02:54
Start Date: 14/Jan/19 02:54
Worklog Time Spent: 10m
Work Description: mxm commented on pull request #7496: [BEAM-6418] Avoid Jenkins memory problems for Flink build targets
URL: https://github.com/apache/beam/pull/7496
The Jenkins test environment is very memory constraint. We get killed by the
host OS (exit code 137) while running tests for multiple FlinkRunner
versions (1.5/1.6/1.7) in parallel. Disabling tests for 1.7 did not fix the
issue. Thus, I'm also disabling test execution for 1.6.
Generally speaking, it seems to be a Jenkins problem because the test JVM can't
acquire the max memory that it has been provided (currently set to max 4GB per
parallel instance) without getting killed by the host OS.
Post-Commit Tests Status (on master branch)
------------------------------------------------------------------------------------------------
Lang | SDK | Apex | Dataflow | Flink | Gearpump | Samza | Spark
--- | --- | --- | --- | --- | --- | --- | ---
Go | [](https://builds.apache.org/job/beam_PostCommit_Go/lastCompletedBuild/) | --- | --- | --- | --- | --- | ---
Java | [](https://builds.apache.org/job/beam_PostCommit_Java/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink/lastCompletedBuild/)<br>[](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Batch/lastCompletedBuild/)<br>[](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Streaming/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark/lastCompletedBuild/)
Python | [](https://builds.apache.org/job/beam_PostCommit_Python_Verify/lastCompletedBuild/) | --- | [](https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow/lastCompletedBuild/) </br> [](https://builds.apache.org/job/beam_PostCommit_Py_ValCont/lastCompletedBuild/) | [](https://builds.apache.org/job/beam_PostCommit_Python_VR_Flink/lastCompletedBuild/) | --- | --- | ---
----------------------------------------------------------------
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:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 184662)
Time Spent: 10m
Remaining Estimate: 0h
> 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
> Time Spent: 10m
> 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)