Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: reduce root-reserve-mb size for maximize-build-space #6064

Merged
merged 7 commits into from
Feb 5, 2024

Conversation

DmitriyLewen
Copy link
Contributor

@DmitriyLewen DmitriyLewen commented Feb 5, 2024

Description

Size of GitHub action ubuntu image has been reduce:
before:

Filesystem Size Used Avail Use% Mounted on 
/dev/root 84G 53G 31G 64% /

now:

Filesystem Size Used Avail Use% Mounted on 
/dev/root 73G 53G 21G 73% /

So we can't get 35840MB - https://github.com/aquasecurity/trivy/actions/runs/7779351592/job/21210359409
So we need to reduce root-reserve-mb value.

Also i played with root-reserve-mb. Size equal 32GB doesn't return error.

Checklist

  • I've read the guidelines for contributing to this repository.
  • I've followed the conventions in the PR title.
  • I've added tests that prove my fix is effective or that my feature works.
  • I've updated the documentation with the relevant information (if needed).
  • I've added usage information (if the PR introduces new options)
  • I've included a "before" and "after" example to the description (if the PR is a user interface change).

@DmitriyLewen DmitriyLewen self-assigned this Feb 5, 2024
Copy link
Collaborator

@knqyf263 knqyf263 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great!

@knqyf263 knqyf263 added this pull request to the merge queue Feb 5, 2024
Merged via the queue into aquasecurity:main with commit 7651bf5 Feb 5, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants