[JIRA] (JENKINS-16287) Race condition in 'build' CLI command

2013-03-12 Thread szikes.a...@gmail.com (JIRA)














































Adam Szikes
 commented on  JENKINS-16287


Race condition in build CLI command















I have the same problem as well.
Jenkins 1.492, XP x86



























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







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




[JIRA] (JENKINS-16287) Race condition in 'build' CLI command

2013-03-08 Thread viktor.tara...@gmail.com (JIRA)














































Viktor Tarasov
 commented on  JENKINS-16287


Race condition in build CLI command















The same for me.
jenkins-1.499, SLES-11-64



























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







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




[JIRA] (JENKINS-16287) Race condition in 'build' CLI command

2013-01-09 Thread ra...@java.net (JIRA)














































Krzysztof Malinowski
 created  JENKINS-16287


Race condition in build CLI command















Issue Type:


Bug



Assignee:


Unassigned


Components:


cli



Created:


09/Jan/13 8:50 AM



Description:


I started a build through jenkins-cli.jar with option to show console and wait for start. It waited to start as long as the build was in queue, but when the build started to build, jenkins-cli exits with exception that log was not found. It seems to me like a race condition between build start, log creation and checking for log in jenkins-cli.


$ java -jar ~/jenkins-cli.jar build project -p build=value -s -v -w
Started project #188
java.io.FileNotFoundException: /jenkins/jenkins_home/jobs/project/builds/2013-01-09_09-43-12/log (No such file or directory)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.init(RandomAccessFile.java:216)
at org.kohsuke.stapler.framework.io.LargeText$FileSession.init(LargeText.java:397)
at org.kohsuke.stapler.framework.io.LargeText$2.open(LargeText.java:120)
at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:210)
at hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:151)
at hudson.model.Run.writeWholeLogTo(Run.java:1253)
at hudson.cli.BuildCommand.run(BuildCommand.java:150)
at hudson.cli.CLICommand.main(CLICommand.java:229)
at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63)
at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)






Environment:


Jenkins 1.498 on RHEL 5 x86_64




Project:


Jenkins



Priority:


Major



Reporter:


Krzysztof Malinowski

























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