-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Sporadic failure of P0645R10_text_formatting_formatting #2449
Comments
The error was:
I don't understand what happened here. Perhaps we should update the test with additional logging, to print the result of |
Happened again in: https://dev.azure.com/vclibs/STL/_build/results?buildId=10119&view=ms.vss-test-web.build-test-results-tab&runId=1184952&resultId=102554&paneView=debug Slightly different line/expression this time (note line 820 instead of line 836):
|
#2494 fortunately printed the actual string before the expected string (the latter was lost due to log truncation, #2557), @statementreply in #2499 (comment) noticed what was wrong with that string indicating a bug in the "huge precision, clamp it and then append zeros later" codepath, I was able to repro it locally and find the root cause in Lines 2510 to 2546 in afe0800
where while (*_Exponent_start != _Exponent) initially reads _Result.ptr (this is past-the-end of what to_chars() wrote), and @barcharcraz has a fix. 🎉
This sporadically failed because the garbage character being read is almost always not the exponent character ( |
This run:
https://dev.azure.com/vclibs/STL/_build/results?buildId=9974&view=logs&j=e5928d94-6045-5a4b-1479-6369daf1c6e1&t=e774f207-3822-5f8e-5e8b-2cdb9d7ebe0b
The subsequent run succeeded, though the change between the runs was in unrelated area, and except of one variable un-shadowing that does not affect anything, it was whitespace/comments change: 2b43c89
The text was updated successfully, but these errors were encountered: