[ 
https://issues.apache.org/jira/browse/BEAM-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442851#comment-16442851
 ] 

Scott Wegner commented on BEAM-4088:
------------------------------------

Thanks, I've responded to the thread: 
[https://lists.apache.org/thread.html/f8c377b7a722218b28217bb11f456b5addc20a90a8ffb17b2077bf8a@%3Cdev.beam.apache.org%3E]

I recommend first debugging to understand exactly why this test fails. Perhaps 
Gradle's execution environment is uncovering a real issue in the code.

The first step should be to see if the test can be implemented with greater 
built-in isolation. This will help ensure our tests are reliable in a variety 
of contexts, including IDE's.

If the test can't be improved, feel free to change the Gradle test 
configuration for the project with a comment why it's necessary.

> ExecutorServiceParallelExecutorTest#ensureMetricsThreadDoesntLeak in PR #4965 
> does not pass in gradle
> -----------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-4088
>                 URL: https://issues.apache.org/jira/browse/BEAM-4088
>             Project: Beam
>          Issue Type: Sub-task
>          Components: testing
>            Reporter: Etienne Chauchot
>            Assignee: Scott Wegner
>            Priority: Major
>
> This is a new test being added to ensure threads don't leak. The failure 
> seems to indicate that threads do leak.
> This test fails using gradle but previously passed using maven
> PR: https://github.com/apache/beam/pull/4965
> Presubmit Failure: 
>  * https://builds.apache.org/job/beam_PreCommit_Java_GradleBuild/4059/
>  * 
> https://scans.gradle.com/s/grha56432j3t2/tests/jqhvlvf72f7pg-ipde5etqqejoa?openStackTraces=WzBd



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to