[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2016-02-02 Thread columbusmon...@me.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gavin Shelley commented on  JENKINS-19743 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Massive parallel builds sometimes cause errors in LogRotation  
 
 
 
 
 
 
 
 
 
 
We see this on 1.611. We too have 100s of parallel jobs running. This pollutes the logs with scary messages. Not sure if it actually affects us apart from logs, but it would be nice to see this resolved in case it is the cause of the occasional unexplained problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2016-01-05 Thread kl...@schniedergers.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Klaus Schniedergers commented on  JENKINS-19743 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Massive parallel builds sometimes cause errors in LogRotation  
 
 
 
 
 
 
 
 
 
 
I am seeing the same (SEVERE: Failed to rotate log), on 1.625.3 (most recent LTS). 
Once the SEVERE log entries start, Jenkins service starts to use all CPU it can get and becomes very slow/unresponsive. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2015-11-06 Thread phrak...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viktor Szathmary commented on  JENKINS-19743 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Massive parallel builds sometimes cause errors in LogRotation  
 
 
 
 
 
 
 
 
 
 
We are also seeing this one (reported above as well). So it seems log rotation for concurrent jobs has a race condition. 
Nov 06, 2015 6:01:49 AM hudson.model.Run execute SEVERE: Failed to rotate log java.io.IOException:Redacted #173213: /redacted/builds/173213 looks to have already been deleted; siblings: [lots of job ids] at hudson.model.Run.delete(Run.java:1483) at hudson.tasks.LogRotator.perform(LogRotator.java:144) at hudson.model.Job.logRotate(Job.java:467) at hudson.model.Run.execute(Run.java:1805) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2015-11-05 Thread phrak...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viktor Szathmary commented on  JENKINS-19743 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Massive parallel builds sometimes cause errors in LogRotation  
 
 
 
 
 
 
 
 
 
 
Using Jenkins ver. 1.636, we are seeing the following exception on a job allowing concurrent builds and having lots of short jobs: 
hudson.model.Run execute SEVERE: Failed to rotate log java.util.NoSuchElementException at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:76) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) at java.util.AbstractMap$2$1.next(AbstractMap.java:396) at hudson.util.RunList.subList(RunList.java:139) at hudson.tasks.LogRotator.perform(LogRotator.java:125) at hudson.model.Job.logRotate(Job.java:467) at hudson.model.Run.execute(Run.java:1805) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2015-03-30 Thread christoph.zausner...@infineon.com (JIRA)














































Nebu Kadnezar
 updated  JENKINS-19743


Massive parallel builds sometimes cause errors in LogRotation
















Change By:


Nebu Kadnezar
(30/Mar/15 3:16 PM)




Attachment:


LogRotator.txt





Attachment:


Run.txt



























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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2015-03-30 Thread christoph.zausner...@infineon.com (JIRA)














































Nebu Kadnezar
 commented on  JENKINS-19743


Massive parallel builds sometimes cause errors in LogRotation















Hi Daniel,

this is not a fix only a working workaround for the issue. See attached Run.txt and LogRotator.txt file for diff patch.



























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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2015-03-25 Thread christoph.zausner...@infineon.com (JIRA)














































Nebu Kadnezar
 commented on  JENKINS-19743


Massive parallel builds sometimes cause errors in LogRotation















We’ve find out that following source changes on Jenkins version 1.606 are a workaround to handle the issue.

1. Adaption on Run.java on the method delete()

Run.java
/**
 * Deletes this build and its entire log
 *
 * @throws IOException
 *  if we fail to delete.
 */
public void delete() throws IOException {

		File rootDir = getRootDir();
if (!rootDir.isDirectory()) {
		LOGGER.log(Level.WARNING, "IOException: " + rootDir + " looks to have already been deleted; siblings: " + Arrays.toString(project.getBuildDir().list()));
//throw new IOException(this + ": " + rootDir + " looks to have already been deleted; siblings: " + Arrays.toString(project.getBuildDir().list()));
}

RunListener.fireDeleted(this);

synchronized (this) { // avoid holding a lock while calling plugin impls of onDeleted
File tmp = new File(rootDir.getParentFile(),'.'+rootDir.getName());

if (tmp.exists()) {
Util.deleteRecursive(tmp);
}
// TODO on Java 7 prefer: Files.move(rootDir.toPath(), tmp.toPath(), StandardCopyOption.ATOMIC_MOVE)
boolean renamingSucceeded = rootDir.renameTo(tmp);
Util.deleteRecursive(tmp);
// some user reported that they see some left-over .xyz files in the workspace,
// so just to make sure we've really deleted it, schedule the deletion on VM exit, too.
if(tmp.exists())
tmp.deleteOnExit();

if(!renamingSucceeded) {
LOGGER.log(Level.WARNING, rootDir+" is in use");
			//throw new IOException(rootDir+" is in use");
		}
LOGGER.log(FINE, "{0}: {1} successfully deleted", new Object[] {this, rootDir});

removeRunFromParent();
}
}
 

2. Adaption on LogRotator.java on the method perform(Job?,? job)

LogRotator.java
public void perform(Job?,? job) throws IOException, InterruptedException {
LOGGER.log(FINE, "Running the log rotation for {0} with numToKeep={1} daysToKeep={2} artifactNumToKeep={3} artifactDaysToKeep={4}", new Object[] {job, numToKeep, daysToKeep, artifactNumToKeep, artifactDaysToKeep});

// always keep the last successful and the last stable builds
Run lsb = job.getLastSuccessfulBuild();
Run lstb = job.getLastStableBuild();

if(numToKeep!=-1) {
// Note that RunList.size is deprecated, and indeed here we are loading all the builds of the job.
// However we would need to load the first numToKeep anyway, just to skip over them;
// and we would need to load the rest anyway, to delete them.
// (Using RunMap.headMap would not suffice, since we do not know if some recent builds have been deleted for other reasons,
// so simply subtracting numToKeep from the currently last build number might cause us to delete too many.)
			
			try
			{
List? extends Run?,? builds = job.getBuilds();
for (Run r : copy(builds.subList(Math.min(builds.size(), numToKeep), builds.size( {
	if (shouldKeepRun(r, lsb, lstb)) {
		continue;
	}
	LOGGER.log(FINE, "{0} is to be removed", r);
	r.delete();
}
			}
			catch(Exception e)
			{
LOGGER.log(FINE, "subList creating failed", e);
			}
}
 



























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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2015-03-25 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-19743


Massive parallel builds sometimes cause errors in LogRotation















Nebu Kadnezar: Could you open a pull request for your fix on GitHub?



























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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2015-03-23 Thread christoph.zausner...@infineon.com (JIRA)














































Nebu Kadnezar
 updated  JENKINS-19743


Massive parallel builds sometimes cause errors in LogRotation
















We've built a Jenkins test project where we can reproduce the issue. Following requirements and project setup describes how you we can reproduce the error deterministically.

Software requirements:

	Jenkins version 1.598
	Build Flow Plugin version 0.9.1
	Java version 1.7.0_72
	C# Script execution engine version 3.8.10.0
	C# Script BuildFlowPluginTest.cs



Test environment:

	Jenkins master runs on a virtual machine with Windows 7 SP1 32 bit
	8 Jenkins slaves physical machines with Windows7 SP1 64 bit
	6 Jenkins slaves virtual machines with Windows 7 SP1 32 bit



Jenkins projects

We have two Jenkins Build Flow projects:

	StressTest_Job
	StressTest_Job_2
Both are executing the same StressTest_SubJob. 




	Create a Build Flow project StressTest_Job and StressTestJob_2 with following configuration like on the screenshots (see attached StressTest_Job_config_1 - StressTest_Job_config_3).
	Create a Jenkins project job similar to the screenshots (see attached StressTest_SubJob_config_1 - StressTest_SubJob_config_3). The only difference to our configuration is the section "Source Code Management". Set this configuration to "None" and add on the section "Build\Command" a copy command which copies the "BuildFlowPluginTest.cs" to the Jenkins slave workspace for execution.



Sample command code for the build section (Windows batch):


@echo off 

xcopy /e "\\Server\project\ BuildFlowPluginTest.cs" %workspace% 

ping %Parameter% -n 10

cscs BuildFlowPluginTest.cs 1

ping %Parameter% -n 10



See also the attached C# script BuildFlowPluginTest.cs code.





Change By:


Nebu Kadnezar
(23/Mar/15 4:14 PM)




Attachment:


BuildFlowPluginTest.cs





Attachment:


StressTest_Job_config_1.png





Attachment:


StressTest_Job_config_2.png





Attachment:


StressTest_Job_config_3.png





Attachment:


StressTest_SubJob_config_1.png





Attachment:


StressTest_SubJob_config_2.png





Attachment:


StressTest_SubJob_config_3.png



























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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2014-11-12 Thread locopelo...@hotmail.com (JIRA)














































Astro Ashtar
 reopened  JENKINS-19743


Massive parallel builds sometimes cause errors in LogRotation
















I get this same issue.

Nov 12, 2014 9:07:25 AM hudson.model.Run execute
SEVERE: Failed to rotate log
java.io.IOException: Run-a-Windows-Job #502803: C:\Program Files (x86)\Jenkins\jobs\Run-a-Windows-Job\builds\2014-11-11_22-58-01 looks to have already been deleted; siblings: .2014-11-11_22-58-01, 2014-11-11_11-09-14, 2014-11-11_11-14-13, 2014-11-11_11-19-54, 2014-11-11_11-19-58, 2014-11-11_11-20-00, 2014-11-11_11-20-01, 2014-11-11_11-20-02, 2014-11-11_11-20-03, 2014-11-11_11-20-04, 2014-11-11_18-08-01, 2014-11-11_18-10-01, 2014-11-11_18-18-01, 2014-11-11_18-20-01, 2014-11-11_18-28-01, 2014-11-11_18-30-01, 2014-11-11_18-38-01, 2014-11-11_18-40-02, 2014-11-11_18-48-01, 2014-11-11_18-58-01, 2014-11-11_19-00-01, 2014-11-11_19-00-02, 2014-11-11_19-08-01, 2014-11-11_19-10-01, 2014-11-11_19-18-01, 2014-11-11_19-20-01, 2014-11-11_19-28-01, 2014-11-11_19-30-01, 2014-11-11_19-38-01, 2014-11-11_19-40-01, 2014-11-11_19-48-01, 2014-11-11_19-58-01, 2014-11-11_20-00-01, 2014-11-11_20-00-02, 2014-11-11_20-08-01, 2014-11-11_20-10-01, 2014-11-11_20-18-01, 2014-11-11_20-20-01, 2014-11-11_20-28-01, 2014-11-11_20-30-01, 2014-11-11_20-38-01, 2014-11-11_20-40-01, 2014-11-11_20-48-01, 2014-11-11_20-58-01, 2014-11-11_21-00-01, 2014-11-11_21-00-03, 2014-11-11_21-08-01, 2014-11-11_21-10-01, 2014-11-11_21-18-01, 2014-11-11_21-20-01, 2014-11-11_21-28-01, 2014-11-11_21-30-01, 2014-11-11_21-38-01, 2014-11-11_21-40-01, 2014-11-11_21-48-01, 2014-11-11_21-58-01, 2014-11-11_22-00-02, 2014-11-11_22-00-03, 2014-11-11_22-08-01, 2014-11-11_22-10-01, 2014-11-11_22-18-01, 2014-11-11_22-20-01, 2014-11-11_22-28-01, 2014-11-11_22-30-01, 2014-11-11_22-38-01, 2014-11-11_22-40-01, 2014-11-11_22-48-01, 2014-11-11_23-00-01, 2014-11-11_23-00-02, 2014-11-11_23-08-01, 2014-11-11_23-10-01, 2014-11-11_23-18-01, 2014-11-11_23-20-01, 2014-11-11_23-28-02, 2014-11-11_23-30-01, 2014-11-11_23-38-02, 2014-11-11_23-40-01, 2014-11-11_23-48-02, 2014-11-11_23-53-02, 2014-11-11_23-58-02, 2014-11-12_00-01-16, 2014-11-12_00-01-23, 2014-11-12_00-08-01, 2014-11-12_00-10-01, 2014-11-12_00-18-01, 2014-11-12_00-20-01, 2014-11-12_00-28-01, 2014-11-12_00-30-01, 2014-11-12_00-38-01, 2014-11-12_00-40-01, 2014-11-12_00-48-01, 2014-11-12_00-58-01, 2014-11-12_01-00-01, 2014-11-12_01-00-02, 2014-11-12_01-08-01, 2014-11-12_01-10-01, 2014-11-12_01-18-01, 2014-11-12_01-20-01, 2014-11-12_01-28-01, 2014-11-12_01-30-01, 2014-11-12_01-38-01, 2014-11-12_01-40-01, 2014-11-12_01-48-01, 2014-11-12_01-58-01, 2014-11-12_02-00-01, 2014-11-12_02-00-02, 2014-11-12_02-08-01, 2014-11-12_02-10-01, 2014-11-12_02-18-01, 2014-11-12_02-20-01, 2014-11-12_02-28-01, 2014-11-12_02-30-01, 2014-11-12_02-38-01, 2014-11-12_02-40-01, 2014-11-12_02-41-27, 2014-11-12_02-41-28, 2014-11-12_02-41-29, 2014-11-12_02-41-30, 2014-11-12_02-41-31, 2014-11-12_02-41-32, 2014-11-12_02-41-33, 2014-11-12_02-41-34, 2014-11-12_02-41-35, 2014-11-12_02-41-36, 2014-11-12_02-41-37, 2014-11-12_02-41-39, 2014-11-12_02-41-40, 2014-11-12_02-41-41, 2014-11-12_02-43-00, 2014-11-12_02-43-06, 2014-11-12_02-43-09, 2014-11-12_02-43-12, 2014-11-12_02-43-18, 2014-11-12_02-43-21, 2014-11-12_02-43-30, 2014-11-12_02-43-31, 2014-11-12_02-43-39, 2014-11-12_02-43-57, 2014-11-12_02-44-09, 2014-11-12_02-44-39, 2014-11-12_02-44-51, 2014-11-12_02-44-54, 2014-11-12_02-44-55, 2014-11-12_02-45-00, 2014-11-12_02-45-03, 2014-11-12_02-45-30, 2014-11-12_02-45-57, 2014-11-12_02-45-58, 2014-11-12_02-46-24, 2014-11-12_02-46-33, 2014-11-12_02-46-42, 2014-11-12_02-46-51, 2014-11-12_02-46-52, 2014-11-12_02-47-00, 2014-11-12_02-47-15, 2014-11-12_02-47-30, 2014-11-12_02-47-31, 2014-11-12_02-47-48, 2014-11-12_02-47-54, 2014-11-12_02-48-01, 2014-11-12_02-48-06, 2014-11-12_02-48-09, 2014-11-12_02-48-21, 2014-11-12_02-48-45, 2014-11-12_02-48-46, 2014-11-12_02-48-48, 2014-11-12_02-49-11, 2014-11-12_02-49-18, 2014-11-12_02-49-39, 2014-11-12_02-50-06, 2014-11-12_02-50-53, 2014-11-12_02-50-57, 2014-11-12_02-51-00, 2014-11-12_02-51-03, 2014-11-12_02-51-16, 2014-11-12_02-51-23, 2014-11-12_02-51-42, 2014-11-12_02-51-48, 2014-11-12_02-52-03, 2014-11-12_02-52-09, 2014-11-12_02-52-15, 2014-11-12_02-52-18, 2014-11-12_02-52-39, 2014-11-12_02-52-42, 2014-11-12_02-52-48, 2014-11-12_02-53-12, 2014-11-12_02-53-39, 2014-11-12_02-53-45, 2014-11-12_02-53-46, 2014-11-12_02-53-54, 2014-11-12_02-53-57, 2014-11-12_02-54-00, 2014-11-12_02-54-15, 2014-11-12_02-54-18, 2014-11-12_02-54-48, 

[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2014-11-12 Thread locopelo...@hotmail.com (JIRA)












































 
Astro Ashtar
 edited a comment on  JENKINS-19743


Massive parallel builds sometimes cause errors in LogRotation
















I get this same issue.

Run on Windows Server 2012. 
Latest Jenkins 1.589 and this has been happening for a while. I always have to restart the jenkins service.

I have about 75 windows slaves. 


Nov 12, 2014 9:07:25 AM hudson.model.Run execute
SEVERE: Failed to rotate log
java.io.IOException: Run-a-Windows-Job #502803: C:\Program Files (x86)\Jenkins\jobs\Run-a-Windows-Job\builds\2014-11-11_22-58-01 looks to have already been deleted; siblings: .2014-11-11_22-58-01, 2014-11-11_11-09-14, 2014-11-11_11-14-13, 2014-11-11_11-19-54, 2014-11-11_11-19-58, 2014-11-11_11-20-00, 2014-11-11_11-20-01, 2014-11-11_11-20-02, 2014-11-11_11-20-03, 2014-11-11_11-20-04, 2014-11-11_18-08-01, 2014-11-11_18-10-01, 2014-11-11_18-18-01, 2014-11-11_18-20-01, 2014-11-11_18-28-01, 2014-11-11_18-30-01, 2014-11-11_18-38-01, 2014-11-11_18-40-02, 2014-11-11_18-48-01, 2014-11-11_18-58-01, 2014-11-11_19-00-01, 2014-11-11_19-00-02, 2014-11-11_19-08-01, 2014-11-11_19-10-01, 2014-11-11_19-18-01, 2014-11-11_19-20-01, 2014-11-11_19-28-01, 2014-11-11_19-30-01, 2014-11-11_19-38-01, 2014-11-11_19-40-01, 2014-11-11_19-48-01, 2014-11-11_19-58-01, 2014-11-11_20-00-01, 2014-11-11_20-00-02, 2014-11-11_20-08-01, 2014-11-11_20-10-01, 2014-11-11_20-18-01, 2014-11-11_20-20-01, 2014-11-11_20-28-01, 2014-11-11_20-30-01, 2014-11-11_20-38-01, 2014-11-11_20-40-01, 2014-11-11_20-48-01, 2014-11-11_20-58-01, 2014-11-11_21-00-01, 2014-11-11_21-00-03, 2014-11-11_21-08-01, 2014-11-11_21-10-01, 2014-11-11_21-18-01, 2014-11-11_21-20-01, 2014-11-11_21-28-01, 2014-11-11_21-30-01, 2014-11-11_21-38-01, 2014-11-11_21-40-01, 2014-11-11_21-48-01, 2014-11-11_21-58-01, 2014-11-11_22-00-02, 2014-11-11_22-00-03, 2014-11-11_22-08-01, 2014-11-11_22-10-01, 2014-11-11_22-18-01, 2014-11-11_22-20-01, 2014-11-11_22-28-01, 2014-11-11_22-30-01, 2014-11-11_22-38-01, 2014-11-11_22-40-01, 2014-11-11_22-48-01, 2014-11-11_23-00-01, 2014-11-11_23-00-02, 2014-11-11_23-08-01, 2014-11-11_23-10-01, 2014-11-11_23-18-01, 2014-11-11_23-20-01, 2014-11-11_23-28-02, 2014-11-11_23-30-01, 2014-11-11_23-38-02, 2014-11-11_23-40-01, 2014-11-11_23-48-02, 2014-11-11_23-53-02, 2014-11-11_23-58-02, 2014-11-12_00-01-16, 2014-11-12_00-01-23, 2014-11-12_00-08-01, 2014-11-12_00-10-01, 2014-11-12_00-18-01, 2014-11-12_00-20-01, 2014-11-12_00-28-01, 2014-11-12_00-30-01, 2014-11-12_00-38-01, 2014-11-12_00-40-01, 2014-11-12_00-48-01, 2014-11-12_00-58-01, 2014-11-12_01-00-01, 2014-11-12_01-00-02, 2014-11-12_01-08-01, 2014-11-12_01-10-01, 2014-11-12_01-18-01, 2014-11-12_01-20-01, 2014-11-12_01-28-01, 2014-11-12_01-30-01, 2014-11-12_01-38-01, 2014-11-12_01-40-01, 2014-11-12_01-48-01, 2014-11-12_01-58-01, 2014-11-12_02-00-01, 2014-11-12_02-00-02, 2014-11-12_02-08-01, 2014-11-12_02-10-01, 2014-11-12_02-18-01, 2014-11-12_02-20-01, 2014-11-12_02-28-01, 2014-11-12_02-30-01, 2014-11-12_02-38-01, 2014-11-12_02-40-01, 2014-11-12_02-41-27, 2014-11-12_02-41-28, 2014-11-12_02-41-29, 2014-11-12_02-41-30, 2014-11-12_02-41-31, 2014-11-12_02-41-32, 2014-11-12_02-41-33, 2014-11-12_02-41-34, 2014-11-12_02-41-35, 2014-11-12_02-41-36, 2014-11-12_02-41-37, 2014-11-12_02-41-39, 2014-11-12_02-41-40, 2014-11-12_02-41-41, 2014-11-12_02-43-00, 2014-11-12_02-43-06, 2014-11-12_02-43-09, 2014-11-12_02-43-12, 2014-11-12_02-43-18, 2014-11-12_02-43-21, 2014-11-12_02-43-30, 2014-11-12_02-43-31, 2014-11-12_02-43-39, 2014-11-12_02-43-57, 2014-11-12_02-44-09, 2014-11-12_02-44-39, 2014-11-12_02-44-51, 2014-11-12_02-44-54, 2014-11-12_02-44-55, 2014-11-12_02-45-00, 2014-11-12_02-45-03, 2014-11-12_02-45-30, 2014-11-12_02-45-57, 2014-11-12_02-45-58, 2014-11-12_02-46-24, 2014-11-12_02-46-33, 2014-11-12_02-46-42, 2014-11-12_02-46-51, 2014-11-12_02-46-52, 2014-11-12_02-47-00, 2014-11-12_02-47-15, 2014-11-12_02-47-30, 2014-11-12_02-47-31, 2014-11-12_02-47-48, 2014-11-12_02-47-54, 2014-11-12_02-48-01, 2014-11-12_02-48-06, 2014-11-12_02-48-09, 2014-11-12_02-48-21, 2014-11-12_02-48-45, 2014-11-12_02-48-46, 2014-11-12_02-48-48, 2014-11-12_02-49-11, 2014-11-12_02-49-18, 2014-11-12_02-49-39, 2014-11-12_02-50-06, 2014-11-12_02-50-53, 2014-11-12_02-50-57, 2014-11-12_02-51-00, 2014-11-12_02-51-03, 2014-11-12_02-51-16, 2014-11-12_02-51-23, 2014-11-12_02-51-42, 2014-11-12_02-51-48, 2014-11-12_02-52-03, 2014-11-12_02-52-09, 2014-11-12_02-52-15, 2014-11-12_02-52-18, 2014-11-12_02-52-39, 2014-11-12_02-52-42, 2014-11-12_02-52-48, 2014-11-12_02-53-12, 2014-11-12_02-53-39, 

[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2014-10-03 Thread o.v.nenas...@gmail.com (JIRA)














































Oleg Nenashev
 commented on  JENKINS-19743


Massive parallel builds sometimes cause errors in LogRotation















 Does this issue still occur on recent Jenkins versions?

I don't know. I was able to reproduce it on 1.532.x, but have not ever tested it on newer versions

 How can this be reproduced? 

Reproduction conditions:

	Fast FreeStyleProject with parallel builds enabled
	Many executors (I've reproduced it on a test server with 16 slaves / 90 executors).



Since there's no votes/watches, we could just close the issue with a "cannot reproduce" state



























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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2014-10-03 Thread o.v.nenas...@gmail.com (JIRA)















































Oleg Nenashev
 resolved  JENKINS-19743 as Cannot Reproduce


Massive parallel builds sometimes cause errors in LogRotation
















Change By:


Oleg Nenashev
(03/Oct/14 8:23 AM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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/d/optout.


[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation

2014-10-02 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-19743


Massive parallel builds sometimes cause errors in LogRotation















Does this issue still occur on recent Jenkins versions? How can this be reproduced? 



























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/d/optout.