[ 
https://issues.apache.org/jira/browse/IMPALA-10570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Smith closed IMPALA-10570.
----------------------------------
    Resolution: Cannot Reproduce

Seems to have become a non-issue in the intervening 2 years.

> FE tests get stuck and eventually time out during UBSAN build
> -------------------------------------------------------------
>
>                 Key: IMPALA-10570
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10570
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 4.0.0
>            Reporter: Laszlo Gaal
>            Priority: Blocker
>              Labels: broken-build
>
> During UBSAN builds on private infrastructure (using CentOS 7.4 as the OS 
> platform) FE tests get stuck, then eventually get killed by the timeout 
> mechanism in buildall.sh. Unfortunately output buffering makes the Jenkins 
> console log slightly confusing, so it is not easy to tell which exact FE test 
> is getting stuck: the timeout and build shutdown sequences seem to be 
> artificially inserted into the middle of the FE build result summary.
> Representative log section:
> {code}
> 01:44:28.496 [INFO] Tests run: 99, Failures: 0, Errors: 0, Skipped: 0, Time 
> elapsed: 0.305 s - in org.apache.impala.analysis.ParserTest
> 01:44:28.496 [INFO] Running org.apache.impala.analysis.ToSqlTest
> 01:44:28.496 [INFO] Tests run: 41, Failures: 0, Errors: 0, Skipped: 0, Time 
> elapsed: 0.88 s - in org.apache.impala.analysis.ToSqlTest
> 01:44:28.496 [INFO] Running org.apache.impala.analysis.Ana
> 01:44:28.496 
> 20:55:34.940 **** run-all-tests.sh TIMED OUT! ****
> 20:55:34.943 
> 20:55:34.943 
> 20:55:34.943 **** Generating backtrace of impalad with process id: 15971 to 
> /data/jenkins/workspace/impala-cdpd-master-core-ubsan/repos/Impala/logs/timeout_stacktrace/impalad_15971_20210308-093840.txt
>  ****
> [..... lots of debug and strack trace output elided for brevity's sake....]
> [.... complete log section for build shutdown elided.....]
> 20:57:13.167 
> /data/jenkins/workspace/impala-cdpd-master-core-ubsan/repos/Impala/common/thrift/MetricDefs.thrift
>  created.
> 20:57:13.167 
> /data/jenkins/workspace/impala-cdpd-master-core-ubsan/impala_schema.mdl 
> created.
> 20:57:13.167 + pg_dump -U hiveuser 
> HMS_data_jenkins_workspace_impala_cdpd_master_core_ubsan_re_cdp
> 20:57:13.167 + exit 1
> 20:57:13.502 Process leaked file descriptors. See 
> https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors 
> for more information
> 20:57:23.505 Build step 'Execute shell' marked build as failure
> 20:57:23.576 lyzeStmtsTest
> 20:57:27.934 [INFO] Tests run: 67, Failures: 0, Errors: 0, Skipped: 0, Time 
> elapsed: 1.999 s - in org.apache.impala.analysis.AnalyzeStmtsTest
> 20:57:27.934 [INFO] Running org.apache.impala.analysis.ExprRewriteRulesTest
> 20:57:27.934 [INFO] Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time 
> elapsed: 0.121 s - in org.apache.impala.analysis.ExprRewriteRulesTest
> [.... rest of the FE test result summary follows.....]
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to