suztomo edited a comment on pull request #14527:
URL: https://github.com/apache/beam/pull/14527#issuecomment-819028655


   `:sdks:java:core:compileTestJava` failed:
   
   ```
   > Task :sdks:java:core:compileTestJava
   
/Users/suztomo/beam/sdks/java/core/src/test/java/org/apache/beam/sdk/metrics/MetricsTest.java:450:
 error: incompatible types: inferred type does not conform to lower bound(s)
       assertThat(
                 ^
       inferred: MetricResult<DistributionResult>
       lower bound(s): CAP#1,MetricResult<DistributionResult>
     where CAP#1 is a fresh type-variable:
       CAP#1 extends Object super: MetricResult<DistributionResult> from 
capture of ? super MetricResult<DistributionResult>
   
   ```
   
   MetricsTest.java:450 has
   
   ```
       assertThat(
           metrics.getDistributions(),
           anyOf(
               // Step names are different for portable and non-portable 
runners.
               hasItem(
                   (Matcher<MetricResult<DistributionResult>>)
                       distributionMinMax(
                           NAMESPACE,
                           "bundle",
                           "MyStep1/ParMultiDo(Anonymous)",
                           10L,
                           40L,
                           isCommitted)),
               hasItem(
                   (Matcher<MetricResult<DistributionResult>>)
                       distributionMinMax(
                           NAMESPACE,
                           "bundle",
                           "MyStep1-ParMultiDo-Anonymous-",
                           10L,
                           40L,
                           isCommitted))));
   ```
   
   Interestingly, the `:sdks:java:core:compileTestJava` succeeds 56 times out 
of 77 attempts (without using build cache):
   
   https://gist.github.com/suztomo/dafc42d93be94822a5c750aec7b5574f
   
   My first time to see such randomness in Java build.
   
   Cham is working on fixing the test.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to