Fix use of shared state in test multiprocessing (#14556)

In #14536 I moved away from solely using environment variables to
control testing options and towards using command line args.  These
command line args set global state in the same way that the env vars do.
However, due to the way multiprocessing works on windows this global
state is not shared with child processes.

On windows the 'spawn' method is used to create children whereas on
unix the 'fork' method us used.

With this change always process the environment variables even when not
running `main`.  I also set those environment variable based on the
command line options so they will always be shared with the child

In the future we should probably transmit out state/option explicitly to
out children but for now this fixes the issue we have been seeing on the
windows roller.
2 files changed
tree: b7f1b0512dc93cf32f163a0dacdfb3a0410a7a8f
  1. .circleci/
  2. .github/
  3. cmake/
  4. docs/
  5. media/
  6. site/
  7. src/
  8. system/
  9. tests/
  10. third_party/
  11. tools/
  12. .clang-format
  13. .coveragerc
  14. .editorconfig
  15. .eslintrc.yml
  16. .flake8
  17. .gitattributes
  18. .gitignore
  19. .gitmodules
  20. .style.yapf
  24. em++
  25. em++.bat
  27. em-config
  28. em-config.bat
  30. emar
  31. emar.bat
  33. embuilder
  34. embuilder.bat
  36. emcc
  37. emcc.bat
  39. emcmake
  40. emcmake.bat
  42. emconfigure
  43. emconfigure.bat
  45. emdump
  46. emdump.bat
  47. emmake
  48. emmake.bat
  50. emprofile
  51. emprofile.bat
  52. emranlib
  53. emranlib.bat
  55. emrun
  56. emrun.bat
  58. emscons
  59. emscons.bat
  61. emscripten-version.txt
  63. emsize
  64. emsize.bat
  67. Makefile
  68. package-lock.json
  69. package.json
  71. requirements-dev.txt

emscripten logo

Main project page:

GitHub CI status: CircleCI

Chromium builder status: emscripten-releases


Emscripten compiles C and C++ to WebAssembly using LLVM and Binaryen. Emscripten output can run on the Web, in Node.js, and in wasm runtimes.

Emscripten provides Web support for popular portable APIs such as OpenGL and SDL2, allowing complex graphical native applications to be ported, such as the Unity game engine and Google Earth. It can probably port your codebase, too!

While Emscripten mostly focuses on compiling C and C++ using Clang, it can be integrated with other LLVM-using compilers (for example, Rust has Emscripten integration, with the wasm32-unknown-emscripten and asmjs-unknown-emscripten targets).


Emscripten is available under 2 licenses, the MIT license and the University of Illinois/NCSA Open Source License.

Both are permissive open source licenses, with little if any practical difference between them.

The reason for offering both is that (1) the MIT license is well-known and suitable for a compiler toolchain, while (2) LLVM‘s original license, the University of Illinois/NCSA Open Source License, was also offered to allow Emscripten’s code to be integrated upstream into LLVM. The second reason became less important after Emscripten switched to the LLVM wasm backend, at which point there isn't any code we expect to move back and forth between the projects; also, LLVM relicensed to Apache 2.0 + exceptions meanwhile. In practice you can just consider Emscripten as MIT licensed (which allows you to do pretty much anything you want with a compiler, including commercial and non-commercial use).

See LICENSE for the full content of the licenses.