]
Mickael Istria commented on JBIDE-18818:
----------------------------------------
{code}Might also be cool to be able to collect up any .log or other Eclipse/Surefire
metadata files; however, I'm not sure you can have a script run if the build times out
/ aborts{code}
The Jenkins archive plugin does that and has been configured to store logs for a while. Cf
Test timeout in org.jboss.tools.jsf.verification.test
-----------------------------------------------------
Key: JBIDE-18818
URL:
https://issues.jboss.org/browse/JBIDE-18818
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsf
Affects Versions: 4.2.1.CR1
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Priority: Blocker
Fix For: 4.2.1.Final
Tests that time out due to blocking UI or other thread lock result in builds that are
recorded as ABORTED [0]. This isn't a problem in terms of publishing new content
because the build runs quickly, publishes the new bits, and THEN starts running tests.
[0]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4....
But where it IS a problem is where we use a buildflow job to run the whole stack of JBT
projects. Buildflows will also abort if they encounter an aborted job [1].
[1]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow...
Why is this a problem? Because when we do a weekend spin (or respin) not all the projects
in the stack are guaranteed to rebuild to verify all the downstream component tests all
still work.
--
If you cannot fix these tests so they run cleanly in Jenkins, please disable them or move
them such that they can still be run LOCALLY using a profile, but will be skipped in
Jenkins.