Closed Bug 1094639 Opened 11 years ago Closed 11 years ago

Runs failing on Ubuntu machines with "Could not initialize class jenkins.model.Jenkins$MasterComputer"

Categories

(Mozilla QA Graveyard :: Infrastructure, defect, P1)

Version 2
x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mihaelav, Assigned: AndreeaMatei)

References

Details

(Keywords: regression)

Several runs failed with: 19:36:30 FATAL: Command execution failed. 19:36:30 java.io.IOException: Remote call on mm-ub-1204-32-4 failed 19:36:30 at hudson.remoting.Channel.call(Channel.java:731) 19:36:30 at hudson.Launcher$RemoteLauncher.launch(Launcher.java:887) 19:36:30 at hudson.Launcher$ProcStarter.start(Launcher.java:353) 19:36:30 at hudson.plugins.xshell.XShellBuilder.perform(XShellBuilder.java:135) 19:36:30 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 19:36:30 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 19:36:30 at hudson.model.Build$BuildExecution.build(Build.java:199) 19:36:30 at hudson.model.Build$BuildExecution.doRun(Build.java:160) 19:36:30 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) 19:36:30 at hudson.model.Run.execute(Run.java:1684) 19:36:30 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 19:36:30 at hudson.model.ResourceController.execute(ResourceController.java:88) 19:36:30 at hudson.model.Executor.run(Executor.java:231) 19:36:30 Caused by: java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer 19:36:30 at hudson.Launcher$LocalLauncher.<init>(Launcher.java:755) 19:36:30 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1016) 19:36:30 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:990) 19:36:30 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 19:36:30 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 19:36:30 at hudson.remoting.Request$2.run(Request.java:328) 19:36:30 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 19:36:30 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 19:36:30 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 19:36:30 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 19:36:30 at hudson.remoting.Engine$1$1.run(Engine.java:63) 19:36:30 at java.lang.Thread.run(Thread.java:745) 19:36:30 Build step 'Invoke XShell command' marked build as failure on Ubuntu machines: mm-ub-1310-32-2 and mm-ub-1204-32-4 We had updates on Ubuntu machines yesterday - see bug 1083130 The times of failures were: * 19:18:17 - 1204-32-2 * 19:18:32 - 1310-32-4 * 19:35:58 - 1310-32-2 * 19:36:30 - 1204-32-4 * 19:37:02 - 1310-32-2
Andreea, this looks like to be a regression as introduced by the updates you did yesterday on the Ubuntu nodes. Can you please investigate? With the release coming up today we have to ensure to not trap into holes. Thanks.
Assignee: nobody → andreea.matei
Blocks: 1083130
Status: NEW → ASSIGNED
Keywords: regression
Priority: -- → P1
Mihaela, did a retrigger of those jobs succeed?
Flags: needinfo?(mihaela.velimiroviciu)
No, it fails the same way. I put those 2 machines offline for investigation
Flags: needinfo?(mihaela.velimiroviciu)
Removed java 7 but that didn't help at first on the 12.04 machine. So I also deleted jenkins folder and after reconnecting the java client, the retrigger passed. Did the same for 13.10.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.