[ 
https://issues.apache.org/jira/browse/IMPALA-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509114#comment-17509114
 ] 

ASF subversion and git services commented on IMPALA-11193:
----------------------------------------------------------

Commit 1739edf2d97009062cb339a3c276f01dbd4d33bd in impala's branch 
refs/heads/master from Yida Wu
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=1739edf ]

IMPALA-11193: Fix assertion failure of ClientCacheTest.MemLeak in CentOS

The assertion failure happens in CentOS because the testcase
reads the virtual memory usage of the current thread from
/proc/thread-self. However, CentOS may not contain this symlink,
therefore the testcase is not able to locate the path and
then triggers the assertion.

This fix changes the path to /proc/self, which is a symlink to the
current process and available in CentOS. Because the testcase
doesn't involve multithreading, it is okay to replace the
/proc/thread-self by /proc/self to detect the memory usage.

Tests:
Passed core tests in CentOS.

Change-Id: I045e91aa9b7d8e1b731e3261f0f18cc932c16f43
Reviewed-on: http://gerrit.cloudera.org:8080/18332
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Assertion fails in ClientCacheTest.MemLeak
> ------------------------------------------
>
>                 Key: IMPALA-11193
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11193
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Daniel Becker
>            Assignee: Yida Wu
>            Priority: Blocker
>              Labels: broken-build
>
> The test {*}ClientCacheTest.MemLeak{*}, introduced in IMPALA-11176, fails in 
> several internal builds.
> h3. Error Message
> {code:java}
> Expected: (mem_before) > (0), actual: 0 vs 0{code}
> h3. Stacktrace
> {code:java}
> /data/jenkins/workspace/impala-cdw-master-staging-core-tsan/repos/Impala/be/src/runtime/client-cache-test.cc:100
> Expected: (mem_before) > (0), actual: 0 vs 0{code}
> Interestingly it is not the main assert that fails but a "precondition", 
> namely EXPECT_GT(mem_before, 0).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to