Test results disappeared since upgrade to 1.500

[Guillaume Bilodeau]

Hi all,

We've been running Jenkins happily since a year now.  One of our jobs runs a Maven build that in turn executes a series of Selenium-based acceptance tests through its FailSafe plugin.  Until version 1.500, test reports have been displayed on the individual build page, with the ability to drill down to individual test results.  Somehow since upgrading to 1.500 these test reports have disappeared from the build page.  Also, hovering over the job weather icon on the main dashboard used to show test stability; it doesn't anymore.

I have verified that the tests are still executed and that the job workspace still contains the FailSafe reports.  Something else is amiss.

Any ideas?

Thanks!

GB

[Christoph Kutzinski]

Could be https://issues.jenkins-ci.org/browse/JENKINS-16573

Do you see any error messages?

Gesendet: Donnerstag, 07. Februar 2013 um 15:34 Uhr
Von: "Guillaume Bilodeau" <guillaume...@gmail.com>
An: jenkins...@googlegroups.com
Betreff: Test results disappeared since upgrade to 1.500

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Stanley, Jason]

Sounds like this perhaps?

 

https://issues.jenkins-ci.org/browse/JENKINS-15156

 

If you stop/start Jenkins.  Do the results appear?

 

 

Thanks

Jason

 

Jason Stanley

Release Engineer/AccuRev Administrator

Tekelec

 

Office - 1 508 804 7038

200 Nickerson Road

Marlborough, MA

01752

--

[Guillaume Bilodeau]

I just restarted Jenkins and still don't see the reports.

The (fresh) logs seem to show an error during initialization:

2013-02-07 11:25:22 jenkins.InitReactorRunner$1 onTaskFailed
GRAVE: Failed SSHD.init
java.lang.Error: java.lang.reflect.InvocationTargetException
	at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124)
	at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:889)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120)
	... 8 more
Caused by: java.lang.NoClassDefFoundError: org/bouncycastle/crypto/modes/SICBlockCipher
	at org.bouncycastle.jcajce.provider.symmetric.util.BaseBlockCipher.engineSetMode(Unknown Source)
	at javax.crypto.Cipher$Transform.setModePadding(Cipher.java:287)
	at javax.crypto.Cipher.getInstance(Cipher.java:572)
	at javax.crypto.Cipher.getInstance(Cipher.java:510)
	at org.apache.sshd.common.util.SecurityUtils.getCipher(SecurityUtils.java:120)
	at org.apache.sshd.common.cipher.BaseCipher.init(BaseCipher.java:59)
	at org.apache.sshd.SshServer.setUpDefaultCiphers(SshServer.java:504)
	at org.apache.sshd.SshServer.setUpDefaultServer(SshServer.java:458)
	at org.jenkinsci.main.modules.sshd.SSHD.start(SSHD.java:82)
	at org.jenkinsci.main.modules.sshd.SSHD.init(SSHD.java:144)
	... 13 more

Could this be related?  One other thing I noticed is that test results for builds executed before the upgrade are accessible.

Thanks,

GB

[Guillaume Bilodeau]

Posted a bug report on the Jenkins JIRA and it was kindly fixed by Chris Kutzinski: https://issues.jenkins-ci.org/browse/JENKINS-16696

On Thursday, February 7, 2013 9:34:07 AM UTC-5, Guillaume Bilodeau wrote: