+1 getting the same issue as well. I saw there were @Ignore on those tests before. If it is not critical and just caused by the way how we do test, does it make sense to put those @Ignores back until it's resolved?
On Tue, Jan 22, 2019 at 3:35 PM Alex Amato <[email protected]> wrote: > I've seen this fail in a few different PRs for different contributors, and > its causing some issues during the presubmit process.. This is a > multithreadred test with a lot of sleeps, so it looks a bit suspicious as > the source of the problem. > > https://builds.apache.org/job/beam_PreCommit_Java_Commit/3688/testReport/org.apache.beam.sdk.io/FileIOTest/testMatchWatchForNewFiles/ > > I filed a JIRA for this issue: > https://jira.apache.org/jira/browse/BEAM-6491?filter=-2 > > > -- ================ Ruoyun Huang
