-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump up C++ version in JNI from c++11 to c++17. #2259
Conversation
932aeec
to
cf34761
Compare
@@ -197,7 +197,7 @@ public void testGetTrainingSize() throws ExecutionException { | |||
|
|||
nativeMemoryCacheManager.get(trainingDataEntryContext, true); | |||
|
|||
assertEquals((float) allocationEntryWeight, nativeMemoryCacheManager.getTrainingSizeInKilobytes(), 0.001); | |||
assertEquals(allocationEntryWeight, nativeMemoryCacheManager.getTrainingSizeInKilobytes(), 1e-3); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fixed this flaky testing where it fails the testing by one.
(float) allocationEntryWeight == 2.1430328E7
nativeMemoryCacheManager.getTrainingSizeInKilobytes() == 21430329
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch
cf34761
to
68d94a0
Compare
Failed rolling update will be fixed in here - #2260 |
Failure in |
Signed-off-by: Dooyong Kim <kdooyong@amazon.com>
68d94a0
to
4e5de3d
Compare
Rolling upgrade 2.11 to 3.00 is failing due to the network error:
|
Signed-off-by: Dooyong Kim <kdooyong@amazon.com> Co-authored-by: Dooyong Kim <kdooyong@amazon.com> (cherry picked from commit a07bad1)
Description
This PR bumped up C++ version in JNI from c++11 to c++17.
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
#2251
Check List
--signoff
.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.