Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review webpack production config #369

Closed
lpirola opened this issue Feb 10, 2017 · 5 comments
Closed

Review webpack production config #369

lpirola opened this issue Feb 10, 2017 · 5 comments
Assignees

Comments

@lpirola
Copy link
Contributor

lpirola commented Feb 10, 2017

No description provided.

@lpirola
Copy link
Contributor Author

lpirola commented Feb 13, 2017

As our build still broke I investigate a bit and found this: jestjs/jest#2179 (comment)

I will try to add more memory to circleci or disable codecoverage. @gabrielrtakeda

@lpirola
Copy link
Contributor Author

lpirola commented Feb 13, 2017

Possible solutions:

jsdom/jsdom#1682 (comment)

@gabrielrtakeda
Copy link
Contributor

@lpirola As discussed, we do not use the jsdom with Jest.. What I suspect is maybe something related with some babel configuration that overheading the memory or something about..

If any of these solutions does not solves our problem with Jest, maybe try to run the tests in "chunks" by module is a way to go.. Or not.. Just a suggestion..

@gabrielrtakeda
Copy link
Contributor

gabrielrtakeda commented Feb 13, 2017

Once, I tried to run tests with the following command:

node --max_old_space_size=4096 --optimize_for_size --max_executable_size=4096 --stack_size=4096 /usr/local/bin/yarn test

But, I do not tested in staging.. I make some googling about the error: FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

And the command above was one of the solutions..

lpirola added a commit that referenced this issue Feb 14, 2017
@lpirola lpirola changed the title Review webpack config to fit our needs Review webpack production config Feb 16, 2017
@lpirola
Copy link
Contributor Author

lpirola commented Mar 10, 2017

I will close this issue, since the error is gone.

@lpirola lpirola closed this as completed Mar 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants