chore(deps): optimize CSI sanity speed during CI

[sergeyberezansky]

TL;DR

Removed -ginkgo.poll-progress-after 3s flag from CSI sanity test configurations

What changed?

Removed the polling progress flag from all test functions in the CSI sanity test script, including:

• directory_volume_no_snapshots
• directory_volume_and_snapshots
• snaphot_volumes_with_2nd_level_shapshots
• filesystem_volumes

How to test?

1. Run the CSI sanity tests using the updated script
2. Verify all test scenarios complete successfully:
   • Directory volume tests without snapshots
   • Directory volume tests with snapshots
   • Snapshot volume tests with second-level snapshots
   • Filesystem volume tests

Why make this change?

The polling progress flag was adding unnecessary overhead to the test execution without providing additional value. Removing it streamlines the test process while maintaining the same level of test coverage and validation.

[sergeyberezansky]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• fix(CSI-322): fix SELinux policy missing on UBI container #447
• feat(CSI-316): support encryption with custom settings per filesystem #444
• fix(CSI-320): print raw entry in log when endpoint address fails to be parsed" #443
• feat(CSI-315): partial support of encrypted volumes for FS backing #442
• chore(deps): optimize CSI sanity speed during CI #438 👈 (View in Graphite)
• refactor(CSI-318): add configurable wait for filesystem / snapshot deletion #437
• refactor(CSI-272): move NFS client registration to APIClient startup rather than on each mount #436
• breaking(CSI-314): remove legacy volume support #435
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Graphite Automations

"Request reviewers once CI passes" took an action on this PR • (01/28/25)

1 reviewer was added to this PR based on Sergey Berezansky's automation.