Closed ax-vasquez closed 3 years ago
Right now, I am running into error 137
, which is an out of memory error. It happens during the Gatsby build step, and is likely a result of it being a dynamic process. I need to look into further configurations to fix this; resource_class
is not even an option with the Cypress orb, so a paid Circle CI plan made no difference :neutral_face:
The only way I could find around error 137 for now is to use the resource_class
feature and set it to xlarge
- lower values sometimes work, but this was the lowest setting I could find that wouldn't hit the error when building the site :grimacing:
I will definitely investigate this later, but for now, it's at least working
The GitHub Action worked, but seemed to have some odd behavior, most-likely stemming from Gatsby's complexity (Circle CI wasn't very easy to twist into working, either).
This adds a working Cypress test workflow, but requires a paid Circle CI plan.