[
https://issues.jboss.org/browse/JBIDE-13429?page=com.atlassian.jira.plugi...
]
Pavol Srna updated JBIDE-13429:
-------------------------------
Summary: setOutput method call doesn't work in testInstall.groovy script (was:
setOutput method doesn't work in testInstall.groovy script)
setOutput method call doesn't work in testInstall.groovy script
---------------------------------------------------------------
Key: JBIDE-13429
URL:
https://issues.jboss.org/browse/JBIDE-13429
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.0.0.Final
Reporter: Pavol Srna
Assignee: Pavol Srna
Fix For: 4.1.0.Alpha1
org.apache.tools.ant.taskdefs.Java setOutput method call doesn't work in
runSWTBotInstallRoutine in testInstall.groovy script. It means that the output from the
process is not redirected to the temporary output file. The temporary output file is then
empty and the errors cannot be detected. And it also means that the testInstall script can
return SUCCESS even if there are errors.
This issue is very well hidden, because testInstall.groovy script is mainly used in
jenkins jobs and all of the jobs publish JUnit reports which will change the job status
into yellow according to the produced xml report.
But if you uncheck the "Publish JUnit report" option, then the job can be blue
even if there are test errors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira