DomGarguilo opened a new issue #154:
URL: https://github.com/apache/accumulo-testing/issues/154
When running the performance tests (via `./bin/performance run`),
ConditionalMutationsPT errors out with the following:
```
Exception in thread "main" java.lang.NumberFormatException: For input
string: "∞"
at
java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2054)
at
java.base/jdk.internal.math.FloatingDecimal.parseDouble(FloatingDecimal.java:110)
at java.base/java.lang.Double.parseDouble(Double.java:543)
at
org.apache.accumulo.testing.performance.tests.ConditionalMutationsPT.runConditionalMutationsTest(ConditionalMutationsPT.java:104)
at
org.apache.accumulo.testing.performance.tests.ConditionalMutationsPT.runTest(ConditionalMutationsPT.java:76)
at
org.apache.accumulo.testing.performance.impl.PerfTestRunner.main(PerfTestRunner.java:51)
```
I think the issue is occuring here:
https://github.com/apache/accumulo-testing/blob/d4151644a9102ccd447a60a402aaeeab748ef230/src/main/java/org/apache/accumulo/testing/performance/tests/ConditionalMutationsPT.java#L153
where a nanosecond value is being converted to a second value. The error
happens when the two nanosecond values, `t1` and `t2`, have a difference of
less than 1000000000 (1 second). `TimeUnit.NANOSECONDS.toSeconds` will convert
the nanos to the nearest second rounding down. So anything less than 1000000000
(1 second) will result in 0 seconds which, in this case, is in the denominator
which returns "∞" and throws an error when being parsed.
I think this can be corrected by manually converting from nanos to seconds.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
