about summary refs log tree commit diff
path: root/src/ci/docker
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-03-30 00:25:41 +0000
committerbors <bors@rust-lang.org>2023-03-30 00:25:41 +0000
commit10338571cfa7c2be0aeed309141ced91454d41e1 (patch)
tree0656a3a63f3fba4acb700119a97dbe40ab481cda /src/ci/docker
parent2fb0e8d162a021f8a795fb603f5d8c0017855160 (diff)
parent7b40eb71a90d93e825e32394d30f199a8492342d (diff)
downloadrust-10338571cfa7c2be0aeed309141ced91454d41e1.tar.gz
rust-10338571cfa7c2be0aeed309141ced91454d41e1.zip
Auto merge of #107221 - kleisauke:getentropy-emscripten, r=ChrisDenton
Use `getentropy()` instead of `/dev/urandom` on Emscripten

`/dev/urandom` is usually available on Emscripten, except when using
the special `NODERAWFS` filesystem backend, which replaces all normal
filesystem access with direct Node.js operations.

Since this filesystem backend directly access the filesystem on the
OS, it is not recommended to depend on `/dev/urandom`, especially
when trying to run the Wasm binary on OSes that are not Unix-based.

This can be considered a non-functional change, since Emscripten
implements `/dev/urandom` in the same way as `getentropy()` when not
linking with `-sNODERAWFS`.
Diffstat (limited to 'src/ci/docker')
-rw-r--r--src/ci/docker/scripts/emscripten.sh4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/ci/docker/scripts/emscripten.sh b/src/ci/docker/scripts/emscripten.sh
index 56dc96283ed..3f5e2c6ff1d 100644
--- a/src/ci/docker/scripts/emscripten.sh
+++ b/src/ci/docker/scripts/emscripten.sh
@@ -20,5 +20,5 @@ exit 1
 
 git clone https://github.com/emscripten-core/emsdk.git /emsdk-portable
 cd /emsdk-portable
-hide_output ./emsdk install 1.39.20
-./emsdk activate 1.39.20
+hide_output ./emsdk install 2.0.5
+./emsdk activate 2.0.5