[internal] typescript-next pipeline runs out of memory
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
We run TypeScript tests against typescript@next nightly. The pipeline (typescript-next) fails in the "Tests TypeScript definitions" step with the following error:
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
Example failure: https://app.circleci.com/pipelines/github/mui/material-ui/136928/workflows/414a50d8-8d10-4e80-b16e-bd1dbc7c6660/jobs/738223?invite=true#step-107-200
Context: the pipeline is all green because we intentionally ignore failures. See https://github.com/mui/material-ui/blob/next/.circleci/config.yml#L363-L371
Search keywords: TypeScript, ci, test
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in .circleci/config.yml around lines 363-371 and inspect the typescript-next pipeline's "Tests TypeScript definitions" step. Reproduce or review the linked CircleCI failure, then verify that the nightly TypeScript definition tests complete without the JavaScript heap out-of-memory error and that the intentional failure handling is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100