[
https://issues.apache.org/jira/browse/BEAM-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812208#comment-16812208
]
Etienne Chauchot edited comment on BEAM-6974 at 4/8/19 8:06 AM:
----------------------------------------------------------------
[~kenn] you closed the ticket and targeted to 2.13. Does that mean that this
fix will not be cherry picked to 2.12 release?
Also please note that without the fix, cassandraIO tests on hadoop platform use
9042 static port. CassandraIOTest (outside hadoop) uses a dynamic port starting
at 9042 (with my other fix). The flakes are due to the order the tests execute.
If CassandraIOTest runs first and takes the port a the beginning of the port
range (ie 9042) and then hadoop cassandra test runs without the fix it will try
to bind 9042 as well. In the other case, If hadoop cassandra test runs first,
it binds 9042 and then when cassandraIOTest runs it binds 9043 so the build is
green.
Long story short, I think we should cherry pick this fix. [~apilloud] WDYT ?
was (Author: echauchot):
[~kenn] you closed the ticket and targeted to 2.13. Does that mean that this
fix will not be cherry picked to 2.12 release?
Also please note that without the fix, cassandraIO tests on hadoop platform use
9042 static port. CassandraIOTest (outside hadoop) uses a dynamic port starting
at 9042 (with my other fix). The flakes are due to the order the tests execute.
If CassandraIOTest runs first and takes the port a the beginning of the port
range (ie 9042) and then hadoop cassandra test runs without the fix it will try
to bind 9042 as well. If hadoop cassandra test runs first, it binds 9042 and
then when cassandraIOTest runs it binds 9043 so the build is green.
Long story short, I think we should cherry pick this fix. [~apilloud] WDYT ?
> [beam_PreCommit_Java_Cron] [:beam-sdks-java-io-cassandra:test][Flake] Test
> fails in native code
> -----------------------------------------------------------------------------------------------
>
> Key: BEAM-6974
> URL: https://issues.apache.org/jira/browse/BEAM-6974
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Mikhail Gryzykhin
> Assignee: Etienne Chauchot
> Priority: Blocker
> Labels: currently-failing
> Fix For: 2.13.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> This test fails often during last several days.
> Suspicion is that same error also fails
> :beam-sdks-java-io-hadoop-input-format:test that flakes as well.
> [https://builds.apache.org/job/beam_PreCommit_Java_Cron/1136/consoleFull]
> [https://builds.apache.org/job/beam_PreCommit_Java_Cron/1133/consoleFull]
> Initial investigation:
> Jenkins doesn't give any error output. Local run fails gradle task stating
> that there's error in native code.
> I was reproing it on version before any of PRs mentioned below (8178 & 8182)
> as well. So there might be some independent issue.
> Dev list thread:
> [https://lists.apache.org/thread.html/80258cf7dcdf404b3de686a5ffdc13a4319c7d2e11698747d62cf5ad@%3Cdev.beam.apache.org%3E]
>
> Relevant PRs that might have influenced the issue:
> [https://github.com/apache/beam/pull/8178]
> [https://github.com/apache/beam/pull/8182]
> ----
> _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)
