[
https://issues.apache.org/jira/browse/BEAM-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismaël Mejía updated BEAM-7469:
-------------------------------
Component/s: runner-dataflow
> [beam_PostCommit_Java_Nexmark_Dataflow] [:sdks:java:testing:nexmark:run] Job
> was unexpectedly updated
> -----------------------------------------------------------------------------------------------------
>
> Key: BEAM-7469
> URL: https://issues.apache.org/jira/browse/BEAM-7469
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, test-failures, testing-nexmark
> Reporter: Andrew Pilloud
> Priority: Major
> Labels: flaky-test
>
> _Use this form to file an issue for test failure:_
> * [Jenkins
> Job|[https://builds.apache.org/job/beam_PostCommit_Java_Nexmark_Dataflow/2880/]]
> * [Gradle Build Scan|[https://scans.gradle.com/s/zuxqe2j2cjaf6]]
> Initial investigation:
> I've seen this a few times over the last few months. This is the pure java
> nexmark.
> {code:java}
> 23:03:32 2019-05-31T06:03:32.895Z FAILED Query4
> ...
> 0004 -1.0 -1.0 -1
> *** Job was unexpectedly updated ***{code}
>
> Looks like we need more logging around what is going on here, but this
> happened right about the same time the first worker VM started.
> ----
> _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
(v8.3.2#803003)
