I’m running the command
free -m when I start my tests, and after they are finished to see how is the memory affected by my code.
However, we see that there is an issue regarding the container that executes our tests. What happens is that the free memory available when the tests start is very little, and our tests are never finished.
Here’s a screenshot of the memory available at bootup:
What we expect
We expect the container to have some free memory for us to use. In fact, we are testing a little React app with
jest and we don’t expect the memory to be impacted heavily by these tests. However, as I said before, they are never finished because the instance goes out of memory.