node-ibm_db: test-issue253 is failing
I 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:
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 16 (10 by maintainers)
Commits related to this issue
- Added Fix for issue #253 #331 — committed to ibmdb/node-ibm_db by rhtpandeyIN 7 years ago
- 2.3.0 * add logs (Bimal Jha) * Add GRANT EXECUTE permissions step for z/OS ODBC (#378) (Joran Siu) * Fix for issue #329, pull #330, #368 (Bimal Jha) * Update tests for z/OS compatiability (Joran ... — committed to ibmdb/node-ibm_db by bimalkjha 6 years ago
- 2.3.1 * Updated test case for issue #357 (#380) (Rohit Pandey) * adding latest code binaries till node 8.X (Rohit Pandey) * Set theme jekyll-theme-cayman (Bimal Kumar Jha) * Fix for issue #377 an... — committed to ibmdb/node-ibm_db by bimalkjha 6 years ago
@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.