You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Alice Chen (JIRA)" <ji...@apache.org> on 2015/07/22 20:20:11 UTC
[jira] [Created] (TRAFODION-1144) LP Bug: 1441717 - Jenkins
regression tests fail without giving a clear diagnostic message
Alice Chen created TRAFODION-1144:
-------------------------------------
Summary: LP Bug: 1441717 - Jenkins regression tests fail without giving a clear diagnostic message
Key: TRAFODION-1144
URL: https://issues.apache.org/jira/browse/TRAFODION-1144
Project: Apache Trafodion
Issue Type: Bug
Components: Build Infrastructure
Reporter: Hans Zeller
Priority: Critical
I'm seeing frequent test failures, not caused by code changes, that either produce no regression logs or successful logs. In both cases, the test is marked as failed, but the output, at least for someone with my mediocre skills of analyzing these test results, doesn't show what went wrong. Here is an example that I've seen more than once:
[PostBuildScript] - Execution post build scripts.
[core-regress-core-ahw2.2] $ /bin/bash /tmp/hudson3132061231974937157.sh
[SCP] Connecting to logs.trafodion.org
[SCP] uploading file: '/srv/static/logs/42/1442/2/gate/core-regress-core-ahw2.2/bf60e5c/Install_Start.log'
[SCP] No file(s) found: corefiles.log
[SCP] ?corefiles.log? doesn?t match anything
Source: http://logs.trafodion.org/42/1442/2/gate/core-regress-core-ahw2.2/bf60e5c/console.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)