Jens A. Koch

Memory out on Travis-CI?

When a build uses too much memory the OOM killer will get in rage and starts to kill processes.
It’s quite difficult to find the real problem, when the process is killed without any information about a reason.
If you want to identify memory issues, consider adding the following lines to your .travis.yml file.

dirty deeds done dirt cheap? err, no…

1) What about creating a new swap file with dd?

 

2) What about cteating a new swap file with fallocate?

OpenVZ does not allow what they call “user defined swap”.
Swap space is only available “as a whole” for the whole system, not for individual VPSes.

Comments Off on Memory out on Travis-CI?

Comments are closed.