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

[Storage][DataMovement] Tests with expected failure cannot run in playback #46717

Open
jalauzon-msft opened this issue Oct 18, 2024 · 0 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files) test-reliability Issue that causes tests to be unreliable

Comments

@jalauzon-msft
Copy link
Member

Certain tests that expect a failure to occur during a transfer are difficult to run in Playback mode as there could be differences in how far the transfer made it before the transfer was cancelled due to failure. This can cause the test to fail for missing recordings when running in playback if the playback test tries to run further than the test did when it was recorded.

We either need to find a way have the recoding file contain all necessary requests so it doesn't matter how far the playback test runs, find a way to ignore the recording failures (if this is okay to do in these tests), or find a way to fail at a known spot, likely through mocking.

@jalauzon-msft jalauzon-msft added the Storage Storage Service (Queues, Blobs, Files) label Oct 18, 2024
@jalauzon-msft jalauzon-msft self-assigned this Oct 18, 2024
@jalauzon-msft jalauzon-msft added Client This issue points to a problem in the data-plane of the library. test-reliability Issue that causes tests to be unreliable labels Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files) test-reliability Issue that causes tests to be unreliable
Projects
None yet
Development

No branches or pull requests

1 participant