[
https://issues.apache.org/jira/browse/BEAM-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743513#comment-16743513
]
Kenneth Knowles commented on BEAM-4638:
---------------------------------------
I think the Gradle Scan is what you have to use. The Jenkins UI is keyed only
on the class name, which is not unique across test runs (and doesn't have to
be).
> Post-commit tests fail job, but report success on detailed view
> ---------------------------------------------------------------
>
> Key: BEAM-4638
> URL: https://issues.apache.org/jira/browse/BEAM-4638
> Project: Beam
> Issue Type: Sub-task
> Components: build-system
> Reporter: Mikhail Gryzykhin
> Assignee: Alan Myrvold
> Priority: Major
> Labels: flake
>
> Some of failed jenkins jobs report tests as failed in job overview, but when
> you click on test, detailed view shows test as passed with some console
> output.
> [https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/923/]
> [https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/923/testReport/junit/org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest/testWrite/]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
