[update: org.eclipse.cdt] !MESSAGE Site XML could not be saved.
[/home/data/users/bfreeman/europa/staging/site.xml (Input/output error)]
I know these I/O errors are lame, and we're working on the problem, but
I have two thoughts:
1. You would increase your odds of a successful build if you used the
build server's local disks (/shared) instead of your home directory
(via NFS). This would also reduce the strain on the NFS server, whose
disk activity lights are ready to burn out :-)
2. Could the exception be trapped, handled and retried instead of
triggering a rebuild? It would seem more efficient to retry the one
small file that failed, like site.xml, rather than re-generating a
whole bunch of disk I/O by rebuilding.
Bjorn Freeman-Benson wrote:
I will re-spin again.
[end of message]
cross-project-issues-dev mailing list
Manager, IT Infrastructure
Eclipse Foundation, Inc. -- http://www.eclipse.org/
Office: 613.224.9461 x224 (Eastern time)