It seems someone (not blaming them in particular) checked in 300mb of Windows 64 binaries in the native client tree. This check-in also seems to have hosed the trybots (they time out while attempting to fetch this data). A /b/slave/linux/build/src/native_client/src/third_party/mingw-w64/mingw-w64-src_20091116.tar.bz2 command timed out: 300 seconds without output, killing pid 15342 elapsedTime=978.505349 update failed, trying 4 more times after 300 seconds
Rather than the obvious rant, I'd like to start a thread on something constructive: What can we do to protect our tree from this sort of thing in the future? - Do we need a trybot for NaCL trunk like we do for WebKit? - Would presubmit scripts help? (I guess that won't help since they're in DEPS?) - Could a style guide that prohibits checking in large binaries help reviewers catch this? - Any other ideas? -- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
