-
Notifications
You must be signed in to change notification settings - Fork 807
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 e2e tests for format options #1769
Add e2e tests for format options #1769
Conversation
Skipping CI for Draft Pull Request. |
f978ff4
to
b52144b
Compare
Code Coverage DiffThis PR does not change the code coverage |
b52144b
to
817b769
Compare
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.
Half the PR seems to be missing, namely the part where we check if the filesystem was actually formatted correctly
817b769
to
7542fb5
Compare
As discussed with @ConnorJC3 @torredil we will validate that custom formatting options were actually applied by mkfs via privileged ubuntu containers running the tune2fs command and regex-Finding their logs in a future PR once testsuite utils are refactored. See #1763 for that approach. A rejected alternative was adding an e2e test confirming that the pod fails to get created when an invalid format option was provided. |
/lgtm |
7542fb5
to
81acc24
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: 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 |
Is this a bug fix or adding new feature?
feature
What is this PR about? / Why do we need it?
Adds end to end tests for format option parameters like
blocksize
andbytesperinode
What testing is done?
ginkgo run --focus="[format]"