-
Notifications
You must be signed in to change notification settings - Fork 623
prepare_stmt_test fails in codegen #1382
Comments
Re-running after pulling from Master 25 May 18, which provides better diagnostics, courtesy of changes by Matt B. 2018-05-25 14:55:19 [/home/proj/master_bin/peloton/test/network/prepare_stmt_test.cpp:41:PrepareStatementTest] INFO - [PrepareStatementTest] Connected to default_database /home/pakhtar/proj/master_bin/peloton/test/network/prepare_stmt_test.cpp:77: Failure |
#0 peloton::codegen::ComparisonTranslator::DeriveValue (this=0x7fffdc009480, codegen/type/type_system.h:37 (gdb) print right |
$21 = (peloton::expression::ComparisonExpression) { |
Possible solutions discussed yesterday.
|
As discussed elsewhere, reason for failing is that libpqxx does not fill type fields in prepare message. We are already casting correctly for types that are known in the binding phase in the network code, but do not do type inference to fix the ones that do not specify types. A workaround would be to use explicit PREPARE with types as SQL in this test case. I have tested that this resolves the issue. |
fixed with #1408 |
Running with:
Master (as of approx. 23 May 2018)
With modified query_compiler.cpp
make check fails, in the prepare_stmt_test
I had, in a different src tree, made some fixes for marshaling types in binary, and was testing to see if they worked, which led to this bug. Since none of my fixes are present, codegen is enabled for VALUE_PARAMETERS, and the test in question does not trigger binary marshaling, this implies something missing or wrong in the codegen support.
See below for available data collected:
prepare_stmt_test.cpp:41:PrepareStatementTest] INFO - [PrepareStatementTest] Connected to default_database
39: prepare_stmt_test: /home/pakhtar/proj/master_bin/peloton/src/codegen/lang/vectorized_loop.cpp:36: peloton::codegen::lang::VectorizedLoop::~VectorizedLoop(): Assertion `(ended_ && "You didn't call lang::VectorizedLoop::LoopEnd()!")' failed.
1/1 Test #39: prepare_stmt_test ................***Exception: Other 0.32 sec
0% tests passed, 1 tests failed out of 1
The text was updated successfully, but these errors were encountered: