-
Notifications
You must be signed in to change notification settings - Fork 87
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
Fixed stringutils test #2154
Fixed stringutils test #2154
Conversation
This build is OK for merge ✅ |
🔴torchvision-inceptionv3_1: FAILED: MIGraphX is not within tolerance - check verbose output🔴cadene-dpn92_1: FAILED: MIGraphX is not within tolerance - check verbose output🔴slim-inceptionv4_1: FAILED: MIGraphX is not within tolerance - check verbose output |
Codecov Report
@@ Coverage Diff @@
## develop #2154 +/- ##
========================================
Coverage 91.48% 91.48%
========================================
Files 424 424
Lines 15871 15873 +2
========================================
+ Hits 14519 14521 +2
Misses 1352 1352
|
Can you add a unit test? The unit tests for this function are here: https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/blob/develop/test/stringutils.cpp |
This fix is for fixing test case issue where brackets are unbalanced by changing src/include/migraphx/stringutils.hpp. Unit test for case where inputs are correct (which checks if output is correct) and test which throws error when input has unbalanced brackets already exists. |
If we already have a test, then why didnt we catch that now when we run the tests? |
I built MIGraphX on Ubuntu20.04 and used develop branch and this test failed. When I rebased my changes on top of develop branch, test_stringutils also failed, but with my changes test on Windows is working. It is not related to OS, this fix is related to algorithm issue: The test fails on interpolate_string_unbalanced case throwing exception with message cannot seek string iterator after end, after the string iterator exceeds a valid range. Part of the code needed to be rewritten, since in its current form it uses undefined behaviour as a condition for a while loop |
Fixed stringutils test with unbalanced brackets