Skip to content
This repository has been archived by the owner on Jun 11, 2020. It is now read-only.

test-runner now shells one node for each dtslint #605

Closed
wants to merge 1 commit into from

Conversation

sandersn
Copy link
Member

@sandersn sandersn commented Apr 16, 2019

It uses the new, local test-worker, which just calls cp.exec(node dtslint) for each dtslint, instead of reusing the same dtslint over and over again.

lodash and reactstrap still run out of memory, but they do that for individual calls to dtslint as well. I think multi-Typescript compiles in ExpectRule may need the same out-of-proc treatment.

Edit: No, types/lodash and types/reactstrap also run out of memory when just compiling with ts 3.4.

It uses the new, local test-worker, which just calls
cp.exec(node dtslint) for each dtslint, instead of reusing the same
dtslint over and over again.

lodash and reactstrap still run out of memory, but they do that for
individual calls to dtslint as well. I think multi-Typescript compiles
in ExpectRule may need the same out-of-proc treatment.
@sandersn
Copy link
Member Author

Actually, when I think about it, only lodash and react are seeing oomemory crashes on CI. lodash itself runs out of memory and reactstrap depends on react.

So I think the root cause is 3.4+ running out of memory on lodash and reactstrap. This PR isn't really needed.

@sandersn sandersn closed this Apr 16, 2019
@sandersn
Copy link
Member Author

Filed microsoft/TypeScript#30973 to track this instead.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant