[
https://issues.apache.org/jira/browse/BEAM-12815?focusedWorklogId=752289&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-752289
]
ASF GitHub Bot logged work on BEAM-12815:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Apr/22 14:19
Start Date: 04/Apr/22 14:19
Worklog Time Spent: 10m
Work Description: damccorm opened a new pull request, #17263:
URL: https://github.com/apache/beam/pull/17263
This adds our failing flink post commit test to the exclusion list and
undoes an attempted fix from #17227 - at the moment I'm going to write up my
findings thus far and stop looking into it since it is lower priority than some
other work.
The fix from #17227 didn't work because it attempts to add args to the flink
shadowJar build step, but that remains cached even when you add args apparently
(which sorta makes sense to me, that way we don't have to rebuild it every
time). The underlying issue is the same as the precommit issue fixed by
https://github.com/apache/beam/pull/17067 but we spin up flink differently in
our post commits and so our config change doesn't affect flink in those
instances.
------------------------
Thank you for your contribution! Follow this checklist to help us
incorporate your contribution quickly and easily:
- [ ] [**Choose
reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and
mention them in a comment (`R: @username`).
- [x] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue, if applicable. This will automatically link the pull request to the
issue.
- [ ] Update `CHANGES.md` with noteworthy changes.
- [x] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
See the [Contributor Guide](https://beam.apache.org/contribute) for more
tips on [how to make review process
smoother](https://beam.apache.org/contribute/#make-reviewers-job-easier).
To check the build health, please visit
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
GitHub Actions Tests Status (on master branch)
------------------------------------------------------------------------------------------------
[](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more
information about GitHub Actions CI.
Issue Time Tracking
-------------------
Worklog Id: (was: 752289)
Time Spent: 1h (was: 50m)
> Flink Go XVR tests fail on TestXLang_Multi: Insufficient number of network
> buffers
> ----------------------------------------------------------------------------------
>
> Key: BEAM-12815
> URL: https://issues.apache.org/jira/browse/BEAM-12815
> Project: Beam
> Issue Type: Bug
> Components: cross-language, sdk-go, test-failures
> Reporter: Daniel Oliveira
> Assignee: Danny McCormick
> Priority: P3
> Fix For: Not applicable
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When running the cross-language test suites () Flink fails on TestXLang_Multi
> with the following error:
> {noformat}
> 19:29:14 2021/08/27 02:29:14 (): java.io.IOException: Insufficient number of
> network buffers: required 17, but only 16 available. The total number of
> network buffers is currently set to 2048 of 32768 bytes each. You can
> increase this number by setting the configuration keys
> 'taskmanager.memory.network.fraction', 'taskmanager.memory.network.min', and
> 'taskmanager.memory.network.max'.
> 19:29:14 2021/08/27 02:29:14 Job state: FAILED
> 19:29:14 --- FAIL: TestXLang_Multi (6.26s){noformat}
> This doesn't seem to be a parallelism problem (go test is run with "-p 1" as
> expected) and is only happening on this specific test.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
