Hi,
The below can be reproducible on s390x platform.
Some steps below that will help you reproduce the issue
1. Use a Rhel 7.1 Host with s390x processor
2. Stack trace below
DirectFunctionCall1() has remaining non-returned values.
Remaining item(s) declared at...
pxffilters_test.c:219
pxffilters_test.c:219
pxffilters_test.c:219
DirectFunctionCall1. func parameter still has values that
haven't been checked.
Remaining item(s) declared at...
pxffilters_test.c:217
pxffilters_test.c:217
pxffilters_test.c:217
arg1 parameter still has values that haven't been checked.
Remaining item(s) declared at...
pxffilters_test.c:218
pxffilters_test.c:218
pxffilters_test.c:218
[ FAILED ] test__list_const_to_str__int
[=============] 1 tests ran
[ PASSED ] 0 tests
[ FAILED ] 1 tests, listed below
[ FAILED ] test__list_const_to_str__int
Do let me know If you have any more questions to reproduce it.
Regards
Ketan Kunde
-----Original Message-----
From: Alex (Oleksandr) Diachenko [mailto:[email protected]]
Sent: Wednesday, March 29, 2017 12:53 PM
To: [email protected]
Subject: Re: Test Case Failures : HAWQ unit test pxffilters
Hi Ketan,
I think I will be able to help you in resolving this issue.
Would you be able to report this issue and attach a stacktrace and environment
to reproduce (like Docker, Vagrant etc)
Regards, Alex.
On Tue, Mar 28, 2017 at 10:03 PM, Ketan Kunde <[email protected]>
wrote:
> Hi ,
>
>
>
> The above setup issue for HAWQ is also resolved.
> I am encountering unit test case failures, failures in module pxffilters.
> for s390x platform.
>
> The below test fails
> unit_test(test_list_const_to_str_int),
> unit_test(test_list_const_to_str_boolean),
> unit_test(test_list_const_to_str_text),
>
> On debugging the below test its observed in file
> 'src/backend/access/ecternal/pxffilters.c'
> in function list_const_to_str()
> At line no 1078 call to function deconstruct_array(arr, INT2OID,
> sizeof (value), true, 's', &dats, NULL, &len); , sets len = 0 Hence
> the 'for' loop starting at line 1084 fails to execute and test fails
>
> The same test when compared on x86 intel is seen set value to len
> other than 0 and hence test cases are passing.
>
> Any inputs on the above cause would be helpful to resolve the failure
> on s390x.
>
> Thanks
> Ketan Kunde
>
>
> DISCLAIMER
> ==========
> This e-mail may contain privileged and confidential information which
> is the property of Persistent Systems Ltd. It is intended only for the
> use of the individual or entity to which it is addressed. If you are
> not the intended recipient, you are not authorized to read, retain,
> copy, print, distribute or use this message. If you have received this
> communication in error, please notify the sender and delete all copies of
> this message.
> Persistent Systems Ltd. does not accept any liability for virus
> infected mails.
>
>
DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the
property of Persistent Systems Ltd. It is intended only for the use of the
individual or entity to which it is addressed. If you are not the intended
recipient, you are not authorized to read, retain, copy, print, distribute or
use this message. If you have received this communication in error, please
notify the sender and delete all copies of this message. Persistent Systems
Ltd. does not accept any liability for virus infected mails.