[email protected] <[email protected]> Findbugs analysis is now only run in the release profile; see: https://github.com/apache/beam/commit/fae52a3f8f4963524c7883450aa740aefaf4a9c6
Adding "-Prelease" to your maven invocation should repro the issue. On Wed, Sep 6, 2017 at 10:23 PM Justin T <[email protected]> wrote: > Hi Scott, > > I'm having trouble reproducing BEAM-407, which is the inconsistent > synchronization in the OffsetRangeTracker.copy. I removed the findbugs > exceptions for the OffsetRangeTracker in the findbugs-filter.xml, and then > ran mvn clean verify. However, it seems that the test cases are still > passing: > > [*INFO*] *Tests run: 14*, Failures: 0, Errors: 0, Skipped: 0, Time > elapsed: 0.002 s - in org.apache.beam.sdk.io.range. > *OffsetRangeTrackerTest* > > The tests that are failing however are related to Hadoop: > > > I checked the surefire-reports and none of these seem to be related to the > OffsetRangeTracker.copy synchronization issue. I am a beginner to the > Apache BEAM project, so your advice would be great. > > Thanks! > > Justin Tumale > >
