Comment #1 on issue 30943 by eric.blake: Need a single DEPS file to describe all chrome builds http://code.google.com/p/chromium/issues/detail?id=30943
Just for the record, I had to add a temporary workaround to the stage_build step on chromeos-linux. The issue was the build was failing a check and not staging the build artifacts to chrome-master.mtv. http://chrome- master.mtv.corp.google.com:8010/builders/chromeos%20official%20linux/builds/256/steps /shell_1/logs/stdio The workaround was to comment out the 'return 0' statement on line 565 of /b/scripts/slave-internal/stage_build.py No changes since last build (r0 <= r0) I made the change locally on the box. The change should persist until/unless someone does an svn revert on that file. More generally, it looks like the script is somehow looking for chrome-official/DEPS and we are now using chrome-official-chromeos/DEPS and hence the failure (maybe anyways) Even more generally it would be beneficial to have individual trigger dirs for each builder, and we may have to solve this particular issue in a more general manner. This was just to stop the bleeding. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
