| commit | 41be9beef52d9e419904bff74c3f529ec627e364 | [log] [tgz] |
|---|---|---|
| author | phoglund@webrtc.org <phoglund@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> | Wed Mar 21 08:01:05 2012 +0000 |
| committer | phoglund@webrtc.org <phoglund@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> | Wed Mar 21 08:01:05 2012 +0000 |
| tree | 5f818a751b938bee33e1a0e2152bd27d54e5902c | |
| parent | 6503ecdc39aac8be42fc4bd1db12ca177e36cfef [diff] |
Put YASM back to the more modern revisions. http://webrtc-cb-linux-master.cbf.corp.google.com:8010/builders/Win32Debug/builds/732/steps/Build%28Debug%29/logs/stdio clearly disproves the hypothesis that rolling back YASM would solve the problem, so I might as well put it back. We will try switching the bot machines to physical machines instead and see if that helps. BUG= TEST= Review URL: https://webrtc-codereview.appspot.com/451014 git-svn-id: http://webrtc.googlecode.com/svn/trunk@1918 4adac7df-926f-26a2-2b94-8c16560cd09d