Currently, we run all the library tests with NodeJS only in runtime-wasm. But this can end up with test breakages getting missed in PR CI builds. The failures are usually in HTTP related library tests, so we could run a handful of these in the regular library tests job on runtime pipeline.
Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.
Issue Details
Currently, we run all the library tests with NodeJS only in `runtime-wasm`. But this can end up with test breakages getting missed in PR CI builds. The failures are usually in HTTP related library tests, so we could run a handful of these in the regular library tests job on `runtime` pipeline.
Currently, we run all the library tests with NodeJS only in
runtime-wasm
. But this can end up with test breakages getting missed in PR CI builds. The failures are usually in HTTP related library tests, so we could run a handful of these in the regular library tests job onruntime
pipeline.