-
Notifications
You must be signed in to change notification settings - Fork 17
Binary value in result leads to crashing of sql-tap tests #293
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
Comments
AFAIR, it can be reproduced with test-run's test |
Allowing accepting binary data in tests. So, an approach was changed from using unicode strings to binary. Fixes: #293
Allowing to accept binary data in tests. So, an approach was changed from using unicode strings to binary. Fixes: #293
If temporary test result file contains non-unicode symbol, it will raise additional logging and will fail the test. Closes: #293
If temporary test result file contains non-unicode symbol, it will raise additional logging 'TAP13 parse failed' and will fail the test. Closes: #293
We decided to provide a better error message instead of the stacktrace. We'll NOT support non UTF-8 data in TAP13 parsing, at least not now: I don't see much value in this functionality. After PR #297 test-run's error reporting should become less confusing:
So, if you have non UTF-8 data in the test output, there are the following options:
|
If temporary test result file contains non-unicode symbol, it will raise additional logging 'TAP13 parse failed' and will fail the test. Closes: #293
This update offers two changes: * More intelligent error reporting for non UTF-8 TAP13 output ([1], [2]). * Restart tarantool server before each test (to avoid unexpected and non-obvious dependencies between tests, see [3]). Removed the pretest_clean suite.ini option: test-run does not read it anymore. [1]: tarantool/test-run#293 [2]: tarantool/test-run#297 [3]: tarantool/test-run#309
This update offers two changes: * More intelligent error reporting for non UTF-8 TAP13 output ([1], [2]). * Restart tarantool server before each test (to avoid unexpected and non-obvious dependencies between tests, see [3]). Removed the pretest_clean suite.ini option: test-run does not read it anymore. [1]: tarantool/test-run#293 [2]: tarantool/test-run#297 [3]: tarantool/test-run#309 (cherry picked from commit 7fa70b6)
This update offers two changes: * More intelligent error reporting for non UTF-8 TAP13 output ([1], [2]). * Restart tarantool server before each test (to avoid unexpected and non-obvious dependencies between tests, see [3]). Removed the pretest_clean suite.ini option: test-run does not read it anymore. [1]: tarantool/test-run#293 [2]: tarantool/test-run#297 [3]: tarantool/test-run#309 (cherry picked from commit 7fa70b6)
This update offers two changes: * More intelligent error reporting for non UTF-8 TAP13 output ([1], [2]). * Restart tarantool server before each test (to avoid unexpected and non-obvious dependencies between tests, see [3]). Removed the pretest_clean suite.ini option: test-run does not read it anymore. [1]: tarantool/test-run#293 [2]: tarantool/test-run#297 [3]: tarantool/test-run#309 (cherry picked from commit 7fa70b6)
How to reproduce:
Result:
The text was updated successfully, but these errors were encountered: