> Now that the aoo-win7 buildbot is running and still failing (with an > exception), I have two kinds of observations. A. The Exception and > Failure itself. See > <https://ci.apache.org/builders/aoo-win7/builds/105> and the bootstrap > exception information from stdio, err.txt, and err.html). There were 2 snapshot builds (#17, #18) and 3 trunk builds (#102-#104) since restart and all got past bootstrap phase. So the question is: what changed to cause the timeout? https://ci.apache.org/builders/aoo-win7 https://ci.apache.org/builders/aoo-w7snap
After bildbot came back online and the first builds: snap #17 and trunk #102, the 'rsync svn files' step failed to clean up the apr makefile. In builds snap #18 and trunk #103-#105 are always the lines: > rsync: delete_file: > unlink(ext_libraries/apr/wntmsci12.pro/misc/build/apr-1.4.5/Makefile.win) > failed: Device or resource busy (16) > rsync: delete_file: rmdir(ext_libraries/apr/wntmsci12.pro/misc/build/apr-1.4.5) failed: Device or resource busy (16) https://ci.apache.org/builders/aoo-win7/builds/105/steps/rsync%20svn%20files/logs/stdio First documented case is snap #9 on august 10. My guess: there are several apr make processes running wild in some kind of loop and blocking resources. Which causes bootstrap to time out. Also, between July 30 and July 31 something caused the 'svn info' step to fail since then, which could be related. Regards -- www.Ok.de - die kostenlose E-Mail Adresse --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
