tree 36a4e7616cc3e091299195c30a83f4dae8c8e460
parent a8263f30af85472c1ea23a01699efc78db9da278
author Sam Clegg <sbc@chromium.org> 1588876971 -0400
committer GitHub <noreply@github.com> 1588876971 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJetFasCRBK7hj4Ov3rIwAAdHIIAI5nIpiCBClhYjKj+j/uBV9N
 QAsD/og0PZbIeVb7243wd/E5arfJIJrwiRwauO0HiAWPPtfq4qSnVJdOcLGaxiSb
 ESxcKfALq4buuw16lwaCcoqVRjZXcfIC6p4JNyyG3vcFp3ZdD3Qs3ReypRVs/fDs
 z9g6pTGyu3zWwlYRT6OhVlAOQMsY/u8TRgmIjeKEQnhLXrVp2iqV6JcCawMNIBrY
 4y818f4cW4vH2ONpno9X1YIPl7UQUQvmU+Qke2rg1lMxLTqUT/FLAhTELZpV7+/M
 A6WWrXMkcAOdS7v6AJKgjCdEtuOPR7tCJtbQgCdC1kqn9q1ZCyqwkYf/RU8tzoY=
 =bsUi
 -----END PGP SIGNATURE-----
 

test.py should require that the SDK be activated (#492)

It was working previously by accident because the tests were
using the defaults such as `$HOME/.emscripten`.  However usage of the
emsdk should really only happen in the emsdk environment where
EM_CONFIG dictates the config location (not just using the default).

This change is needed as precursor to making `--embedded` the default
(in this case the config doesn't live in `$HOME/.emscripten`).