[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Another excerpt with newest build: Jan 29, 2015 8:50:35 AM WARNUNG jenkins.model.RunIdMigrator doMigrate failed to process d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\2014-10-16_10-32-01 java.io.IOException: d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\68 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5995 Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5996 Jan 29, 2015 8:50:35 AM WARNUNG jenkins.model.RunIdMigrator doMigrate failed to process d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\2014-11-05_16-13-26 java.io.IOException: d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\69 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5997 Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5998 Jan 29, 2015 8:50:35 AM INFO jenkins.model.RunIdMigrator migrate Migrating build records in d:\NightlyBuilds\Jenkins\jobs\KomalogWin - 14.01-dev\builds Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 124 Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 128 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Steve Haworth commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Build #3957 Log extract... 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-10_17-23-06 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\273 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\GEMTEST_Page_84\builds\2014-12-23_14-42-31 java.io.IOException: C:\Jenkins\jobs\GEMTEST_Page_84\builds\1420 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-26_13-03-35 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\288 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Jenkins is running on Running on a Virtual Machine with - Windows Server 2008 R2 Standard with Service Pack 1 Java version is - Java Standard Edition Version 8 Update 31 NOTE: Tried experiment if I manually delete the shortcut directories in a job directory then migration is okay 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
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Steve Haworth edited a comment on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Build #3957 Log extract... 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-10_17-23-06 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\273 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\GEMTEST_Page_84\builds\2014-12-23_14-42-31 java.io.IOException: C:\Jenkins\jobs\GEMTEST_Page_84\builds\1420 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-26_13-03-35 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\288 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Jenkins is running on a Virtual Machine with - Windows Server 2008 R2 Standard with Service Pack 1 Java version is - Java Standard Edition Version 8 Update 31 NOTE: Tried experiment... if I manually delete the shortcut directories in a job directory then migration is okay 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
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 tdtappe Well I will check once I get a post-XP test system up. My reading of the code in older versions of Jenkins is that it would never create such a symlink when running on Java 6, but I may have missed something. Steve Haworth Odd. The build is recorded as having been created by Jenkins 1.590, so before the switch, yet it has timestamp and no number, like the new format, but no id, like the old format. The migrator intentionally tries the folder rename before the build.xml rewrite, so it should not have been the result of an error midway through migration. So I have no explanation for how you got there and hope this is rare enough. 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Daniel Beck commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Jesse: Could the unexpected XML come from running the unmigration script? 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 OK, the 116+ builds are either new, or got correctly migrated, but then we also got skipping deletion of directory 4 where this one was an old build with a SYMLINKD that did not get migrated. 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Jesse Glick updated JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Change By: Jesse Glick (28/Jan/15 3:41 PM) Summary: Buildrecordsnotmigrateddueto“failedtorename ”onWindowsesp.onJava6 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 The question is how you even got these build number symlinks to begin with—as far as I know they are not created when you run Jenkins on Windows using Java 6! (Even if the Windows system supports symlinks generally; IIRC XP does not, and newer systems may or may not.) The only way I can think to make them appear is to run 1.596- using Java 7, at least for a while, then run 1.597+ using Java 6. 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 I am almost 100% sure that there never has been another Java version than 6 (since 2010) on that machine. 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 BTW I could most probably switch to Java 7 or even 8 on that machine if it might solve all my problems. But then we (you) wouldn't have a problematic real time scenario any longer to test with Java 6!? 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Steve Haworth commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Attached 2014-11-26_03-40-28 build.xml This is one of the files indicated in log "jenkins.err.log_on-startup.txt" as having no number. 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Steve Haworth updated JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Change By: Steve Haworth (28/Jan/15 5:53 PM) Attachment: 2014-11-26_03-40-28build.xml 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-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Actually not: Datentr„ger in Laufwerk D: ist DATEN Volumeseriennummer: 1225-FEC9 Verzeichnis von D:\NightlyBuilds\Jenkins\jobs\KomalogWin - 14.02.00-patched\builds Mi 28.01.2015 16:12DIR . Mi 28.01.2015 16:12DIR .. Di 20.01.2015 02:57DIR 116 Sa 24.01.2015 02:51DIR 121 Di 27.01.2015 02:51DIR 122 Mi 28.01.2015 02:55DIR 123 Fr 29.08.2014 03:25DIR 2014-08-29_03-51-39 Fr 29.08.2014 02:51SYMLINKD 4 2014-08-29_03-51-39 Fr 19.12.2014 02:57 2 lastFailedBuild Mi 28.01.2015 02:55 3 lastStableBuild Mi 28.01.2015 02:55 3 lastSuccessfulBuild Mi 27.08.2014 07:19 2 lastUnstableBuild Fr 19.12.2014 02:57 2 lastUnsuccessfulBuild Mi 28.01.2015 16:12 0 legacyIds 6 Datei(en), 12 Bytes 8 Verzeichnis(se), 769.188.323.328 Bytes frei 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.
