[
https://issues.apache.org/jira/browse/IMPALA-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503606#comment-16503606
]
Philip Zeyliger commented on IMPALA-7129:
-----------------------------------------
I couldn't spot anything obvious, so I'm reproducing. (I'm stumped about how
custom cluster tests may be clearing their environment, since
start-impala-cluster.py certainly seems to depend on $IMPALA_HOME all over the
place, but reproduction will hopefully tell me.) If you're blocked, I'd be
happy to prepare a partial revert. The other workaround is to set UBSAN_OPTIONS
explicitly.
> Can't start catalogd in tests under UBSAN
> ------------------------------------------
>
> Key: IMPALA-7129
> URL: https://issues.apache.org/jira/browse/IMPALA-7129
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.0
> Reporter: Jim Apple
> Assignee: Philip Zeyliger
> Priority: Major
>
> https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/2377/testReport/junit/custom_cluster.test_admission_controller/TestAdmissionController/test_require_user/
> This custom cluster test failed
> https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/2377/artifact/Impala/logs_static/logs/custom_cluster_tests/catalogd-error.log/*view*/
> {{UndefinedBehaviorSanitizer: failed to read suppressions file
> '/home/ubuntu/Impala/be/build/debug/service/./bin/ubsan-suppressions.txt'}}
> A number of other tests failed, too, and I suspect it's
> https://github.com/apache/impala/commit/48625335d220566a1d69e65fb34bfca9a7dc3cff
> that broke it. I guess maybe {{IMPALA_HOME}} is not set in some tests?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
