Update yasm to 1.3.0 on the bots.
As of https://chromium-review.googlesource.com/#/c/608869/, Chromium is
now using yasm 1.3.0, which means we can rely on it.
This is upstream's yasm-1.3.0-win32.exe which has a SHA-512 hash of:
850b26be5bbbdaeaf45ac39dd27f69f1a85e600c35afbd16b9f621396b3c7a19863ea3ff316b025b578fce0a8280eef2203306a2b3e46ee1389abb65313fb720
(I'm using such a humungous hash because if one searches for it on
Google, there is evidence that someone else in the world downloaded the
same hash.)
Change-Id: I4674080dd07d3e07f399a67e767a00fc67d4aa63
Reviewed-on: https://boringssl-review.googlesource.com/19104
Commit-Queue: David Benjamin <davidben@google.com>
Commit-Queue: Steven Valdez <svaldez@google.com>
Reviewed-by: Steven Valdez <svaldez@google.com>
diff --git a/util/bot/UPDATING b/util/bot/UPDATING
index 43aa30a..6b8b48e 100644
--- a/util/bot/UPDATING
+++ b/util/bot/UPDATING
@@ -54,7 +54,7 @@
Use the release at http://yasm.tortall.net/Download.html labeled
"Win32 .exe". The download will be named yasm-VERSION-win32.exe.
- The current revision is yasm-1.2.0-win32.exe.
+ The current revision is yasm-1.3.0-win32.exe.
Finally, update sde-linux64.tar.bz2 by downloading the latet release from intel
at
diff --git a/util/bot/yasm-win32.exe.sha1 b/util/bot/yasm-win32.exe.sha1
index 5b8c9aa..542a6c9 100644
--- a/util/bot/yasm-win32.exe.sha1
+++ b/util/bot/yasm-win32.exe.sha1
@@ -1 +1 @@
-4c4d1951181a610923523cb10d83d9ae9952fbf3
\ No newline at end of file
+8374a6a1d6a240a3baa771ffd61b3bc096ccd11f
\ No newline at end of file
