{"push_id":1468396674,"size":1,"distinct_size":1,"ref":"refs/heads/fix-tmpfs-sizes","head":"b1c018605547dd347b9f63f833b52d8eca01f452","before":"c4eea8e971eac78105d3fe7c6031162672f0f91a","commits":[{"sha":"b1c018605547dd347b9f63f833b52d8eca01f452","author":{"name":"Olav Philipp Henschel","email":"e65419d5528963ced74dda345f7ae2ecb2cafe89@linux.vnet.ibm.com"},"message":"Update mock's tmpfs plugin parameters with realistic values\n\nWe had a misconception on the meaning of the parameters to the tmpfs\nplugin. The \"required_ram_mb\" parameter must be greater than the\n\"max_fs_size\" parameter, to make sure the system has enough RAM to mount\nthe whole tmpfs. Otherwise, the build may try to use more memory than\nwhat is available and crash with an \"out of memory\" failure.\n\nWe've found out that guests running the whole build grow their\nexpandable virtual disks to aproximately 30GB, so the max file system\nsize must be at least that. With a little slack and adding 8GiB for\n\"normal\" RAM usage, we get to the defined value of approximately 40GiB\nof required RAM to enable the tmpfs plugin.","distinct":true,"url":"https://api.github.com/repos/olavphibm/builds/commits/b1c018605547dd347b9f63f833b52d8eca01f452"}]}
{"actor":{"display_login":"olavphibm"}}