It was disabled out of an abundance of caution, but the test can probably just be re-enabled. I tried running it locally and it worked fine. TestParseDepthLimit definitely cannot be trivially re-enabled.
The text was updated successfully, but these errors were encountered:
Because it requires a not insignificant amount of memory to run. Also
remove the WASM-only skip from TestScopeDepthLimit, which is less
Auto-Submit: Roland Shoemaker <email@example.com>
Reviewed-by: Bryan Mills <firstname.lastname@example.org>
TryBot-Result: Gopher Robot <email@example.com>
Run-TryBot: Roland Shoemaker <firstname.lastname@example.org>