test-issue253 is failing
See original GitHub issueI am seeing a failure after v2.1.0
release:
Running test for [DB2] : test-issue253 ... fail
Stdout:
Stderr:
assert.js:81
throw new assert.AssertionError({
^
AssertionError: '[IBM][CLI Driver][DB2/AIX64] SQL0180N The syntax of the string representation of a datetime value is incorrect. SQLSTATE=2200 == '[IBM][CLI Driver][DB2/LINUXX8664] SQL0180N The syntax of the string representation of a datetime value is incorrect. SQLSTATE
at /home/alk/tmp/node-ibm_db/test/test-issue253.js:24:20
at /home/alk/tmp/node-ibm_db/lib/odbc.js:367:61
Useful Links:
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (10 by maintainers)
Top Results From Across the Web
Fix client test · Issue #253 · dragonflyoss/Dragonfly2 · GitHub
Feature request: Current, when run test with -race, some tests failed. Need to fix client test. Use case: N/A UI Example: N/A.
Read more >reactor.netty.http.server.HttpServerResponse java ... - Tabnine
isDebugEnabled()) { logger.debug("Failed to get request URI: " + ex.getMessage()); } reactorResponse.status(HttpResponseStatus.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@al-k21 This test case fails only if target database server is other than DB2/LINUXX8664. You can ignore this failure as of now. It is only test case issue not a bug. I think @rhtpandeyIN will correct the test file. Thanks.
@gibfahn ,
I think I didn’t explain it well before, sorry for the confusion. What I meant was, while checking the error content in the test case (at the time of assertion) I will not check the driver specific part, as this test case do not depends on any driver specific situations hence error will be generic and same for all (and I am not going to change error returned by the driver). This test case is failing because of “name/platform-name of the driver” not because of the error message or error code. To be very specific it’s just a test case assertion change not the driver related or code related changes. I hope now I am clear. Thanks.