[
https://issues.apache.org/jira/browse/BEAM-6681?focusedWorklogId=199570&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-199570
]
ASF GitHub Bot logged work on BEAM-6681:
----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Feb/19 10:38
Start Date: 16/Feb/19 10:38
Worklog Time Spent: 10m
Work Description: adude3141 commented on issue #7861: [BEAM-6681]
increase maxHeapSize for apex validatesrunner test
URL: https://github.com/apache/beam/pull/7861#issuecomment-464334885
@tweise This is indeed an interesting question.
If we talk about 'parallel execution' we should clarify semantics here. What
we usually mean, is that `--parallel` flag on gradle. AFAIU this enables 'only'
parallel execution of tasks. Which of course implies that it should *not*
change memory requirement of a single test task, e.g.
`apexRunner.validatesRunnerBatch`. We did not change anything here - afaik.
I might have introduced some confusion on the discussion about Jacoco
report. On gradle 4 it was not possible to execute coverage with parallel
execution *and* build caching. We had to choose, and have chosen to disable the
build cache *for java precommit tests only*. The build cache got reenabled with
gradle 5, otherwise *nothing* has changed.
So this issue is caused by to aggressive reduction of maxJavaHeap, which we
fix here. We just revealed something here which was probably hidden by gradle4
defaults. I d like to get this change into the codebase first and will look
into the open questions later on
- higher mem consumption on apex runner compared to flink/spark
- runtime decrease on flink runner validatesRunnerBatch
- runtime difference between spark batch and streaming
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 199570)
Time Spent: 50m (was: 40m)
> [JobName] [TestName] Failure summary
> ------------------------------------
>
> Key: BEAM-6681
> URL: https://issues.apache.org/jira/browse/BEAM-6681
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Ankur Goenka
> Assignee: Michael Luckey
> Priority: Major
> Labels: currently-failing
> Time Spent: 50m
> Remaining Estimate: 0h
>
> _Use this form to file an issue for test failure:_
> *
> https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex/3020/
> * https://gradle.com/s/h3m6nxrz4sexg
> * [Test source code|TODO]
> Initial investigation:
> (Add any investigation notes so far)
> ----
> _After you've filled out the above details, please [assign the issue to an
> individual|https://beam.apache.org/contribute/postcommits-guides/index.html#find_specialist].
> Assignee should [treat test failures as
> high-priority|https://beam.apache.org/contribute/postcommits-policies/#assigned-failing-test],
> helping to fix the issue or find a more appropriate owner. See [Apache Beam
> Post-Commit
> Policies|https://beam.apache.org/contribute/postcommits-policies]._
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
