You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Xiang Sheng (JIRA)" <ji...@apache.org> on 2016/11/03 01:12:58 UTC
[jira] [Assigned] (HAWQ-1138) Unit test failed when make
unittest-check if enable '--enable-cassert' option in hawq configure
[ https://issues.apache.org/jira/browse/HAWQ-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiang Sheng reassigned HAWQ-1138:
---------------------------------
Assignee: Xiang Sheng (was: Jiali Yao)
> Unit test failed when make unittest-check if enable '--enable-cassert' option in hawq configure
> -----------------------------------------------------------------------------------------------
>
> Key: HAWQ-1138
> URL: https://issues.apache.org/jira/browse/HAWQ-1138
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Tests
> Reporter: Xiang Sheng
> Assignee: Xiang Sheng
>
> reproduce:
> 1. ./configure --enable-debug --enable-cassert
> 2. make -j8 && make install && hawq start cluster -a
> 2. cd src/backend
> 3. make unittest-check
> unittest failed 1 case :
> [ RUN ] test__MemoryAccounting_GetAccountName__Validate
> No entries for symbol ExceptionalCondition.
> ERROR: ../../../../../src/test/unit/mock/backend/utils/error/assert_mock.c:26 - Could not get value to check parameter conditionName of function ExceptionalCondition
> Previously declared parameter value was declared at memaccounting_test.c:1320
> [ FAILED ] test__MemoryAccounting_GetAccountName__Validate
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)