Created attachment 103696 [details]
Hudson v1.386 (behind HTTP proxy).
If I get Test Failures of Hudson job from NB, nothing happens. There's no message in the server log.
Attaching IDE log (logging with FINE level).
Product Version: NetBeans IDE Dev (Build 101207-82ef52c60670)
Java: 1.6.0_22; Java HotSpot(TM) 64-Bit Server VM 17.1-b03
System: Linux version 2.6.35-23-generic running on amd64; UTF-8; cs_CZ (nb)
Very likely the same problem.
*** This bug has been marked as a duplicate of bug 193008 ***
Have to reopen this one because it seems that it is not a duplicate of #193008 (still, nothing happens if one requests Test Failures).
Let me know what I can do or provide in order to fix this issue.
I need some way to reproduce the problem. Or at a minimum, log messages from after the fix of bug #193008. (I see no indication in your last log that the action was even run.)
Sorry, I don't have time for it now, I will reopen this issue soon. Thanks.
I found the cause; I have debugged org.netbeans.modules.hudson.ui.actions.ShowFailures class and the first (and the only) element in the returned XML is "failures" (I will attach the whole file, it is only one empty element) so it is ignored by <anonymous>.startElement() method (maybe some WARNING could be logged? that's why nothing was visible in the IDE log).
Unfortunately I have no idea why the returned stream contains just one empty element (I just verified via browser that there were 44 failed tests for the given test run) - don't you have any idea, Jesse? We have Hudson ver. 1.386.
Thanks a lot!
Created attachment 104136 [details]
content of the returned stream
Any progress, please?
Created attachment 104740 [details]
sample of test report
Diagnosis by reporter shows that junitResult.xml exists and is loaded correctly by a test Hudson instance, but for some reason no <errorStackTrace> is produced in .../testResult/api/xml output from the real server. So the problem is likely some kind of bug in Hudson. (Inspection of CaseResult source confirms that a test is "failed" iff errorStackTrace != null, and the test in question is just a regular JUnit 3.x test run by Surefire.) $build.testResultAction.failedTests.errorStackTrace works in Groovy console, so perhaps there is some problem in the Stapler layer.
NB bug is that IDE shows nothing in this case. Should at least show a dialog box explaining that there is some problem in the remote API.