[ https://issues.apache.org/jira/browse/IMPALA-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664125#comment-16664125 ]
ASF subversion and git services commented on IMPALA-5031: --------------------------------------------------------- Commit 1d72c7584fd33746b17826c1dc54a1819fce9ec5 in impala's branch refs/heads/master from [~jbapple] [ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=1d72c75 ] IMPALA-5031: Increase backend test timeout under UBSAN_FULL When codegen is run with ubsan, backend tests slow down dramatically. This patch increases the timeout to four hours in when UBSAN_FULL is the build type. This limit is approached by expr-test, which takes almost three hours under UBSAN_FULL. Change-Id: I3eee4c2b3affc9d65d86c043fcc382d7248adf3e Reviewed-on: http://gerrit.cloudera.org:8080/11764 Reviewed-by: Jim Apple <jbapple-imp...@apache.org> Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com> > UBSAN clean and method for testing UBSAN cleanliness > ---------------------------------------------------- > > Key: IMPALA-5031 > URL: https://issues.apache.org/jira/browse/IMPALA-5031 > Project: IMPALA > Issue Type: Task > Components: Backend, Infrastructure > Affects Versions: Impala 2.9.0 > Reporter: Jim Apple > Assignee: Jim Apple > Priority: Minor > > http://releases.llvm.org/3.8.0/tools/clang/docs/UndefinedBehaviorSanitizer.html > builds are supported after https://gerrit.cloudera.org/#/c/6186/, but > Impala's test suite triggers many errors under UBSAN. Those errors should be > fixed and then there should be a way to run the test suite under UBSAN and > fail if there were any errors detected. -- 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