-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add tests for trim reducing space usage on filesystem and block storage #5622
Conversation
Draft until #5578 is merged. |
Looks good :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks ok. Please add the requirement CNV-5750 to the test:
@kgoldbla: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/lgtm |
/approve cancel |
@maya-r I think the toolbox should be baked into kubevirtci for |
/lgtm cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Signed-off-by: Maya Rashish <mrashish@redhat.com>
Signed-off-by: Maya Rashish <mrashish@redhat.com>
Signed-off-by: Maya Rashish <mrashish@redhat.com>
On both block (OCS) and filesystem (local storage) Signed-off-by: Maya Rashish <mrashish@redhat.com>
the goveralls failure seems to originate from #5694, rather than from this PR. |
Done :) |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mhenriks The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
1 similar comment
/retest |
Test flow:
Boot Fedora
Write large file
Write down space usage
Write small file
Delete large file, trim /
Write down space usage again
If preallocated, we expect no change in disk usage.
If trim is expected to work (default) we expect a decrease.
If trim isn't expected to work (thick provisioned) we expect an increase, due to the small file.
Both OCS and local storage are tested.
Depends on #5578 to be merged first.
What this PR does / why we need it:
Testing actual end-to-end functionality.
Release note: