[
https://issues.apache.org/jira/browse/IMPALA-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-3792.
-----------------------------------
Resolution: Invalid
This is mostly about cloudera infrastructure. There was some recent work that
helped with this like IMPALA-7399 and jenkins/finalize.sh
> Test failures not obvious through Jenkins
> -----------------------------------------
>
> Key: IMPALA-3792
> URL: https://issues.apache.org/jira/browse/IMPALA-3792
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 2.7.0
> Reporter: Harrison Sheinblatt
> Priority: Critical
> Labels: test-infra
>
> http://sandbox.jenkins.sf.cloudera.com/view/Impala/view/Evergreen-cdh5-trunk/job/impala-cdh5-trunk-core-local-filesystem/102/
> Several problems:
> # The job failed, but there's no message at the end of the console out
> explaining why
> # The summary page in Jenkins shows that all tests pass -- no failures. It's
> a known issue that the junit plugin is not finding all the test results (it
> caps at 999), so potentially this is caused by that
> # The run test scripts don't log clearly so it's hard to figure out if a
> failure is caused by a test failure or a jenkins script failure. For
> example, bin/run-all-tests.sh with set TEST_RET_CODE to 1 for failures of
> scripts, but these scripts aren't traced, there's no echo of found issues,
> and there's no summary at the end. So, if it is a failure, there's no way to
> separate that failure from some other jenkins script failure causing the job
> failure.
> # Linking to IMPALA-1255: run-tests.py should give a results summary which
> will help
--
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
