fixing the memory issue in auto-cherry-pick GHA

[omkarkhatavkar]

PR Description

Summary

This PR addresses an issue related to out-of-memory errors during the execution of GitHub Actions workflows. To mitigate this problem, we're introducing a step to set up swap space.

Changes Made

• Added a new step to the workflow that sets up swap space with a size of 10GB.

Context

In certain resource-intensive workflows, such as those involving large builds or data processing tasks, GitHub Actions runners may encounter out-of-memory errors. These errors can disrupt the workflow and cause it to fail.

To avoid such errors and ensure the smooth execution of workflows, we have introduced a step that configures a swap space of 10GB. Swap space provides additional virtual memory, which can be used when the physical memory is exhausted, thereby preventing out-of-memory errors.

[synkd]

Non-blocking, but do we have a way to monitor whether runners are actively swapping when under memory pressure?

[omkarkhatavkar]

Non-blocking, but do we have a way to monitor whether runners are actively swapping when under memory pressure?

This will by default swap memory space and can be seen in the logs after we merge this https://github.com/pierotofy/set-swap-space/blob/master/action.yml#L32 line it shows after modification.