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

Investigate storage transient test failures #4196

Closed
mikeharder opened this issue Jul 8, 2019 · 7 comments
Closed

Investigate storage transient test failures #4196

mikeharder opened this issue Jul 8, 2019 · 7 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)

Comments

@mikeharder
Copy link
Member

Storage tests have transient failures. To mitigate, #4162 added global retries, but a more narrowly-scoped retry mechanism would be preferable to avoid hiding other transient issues and more closely represent expected customer usage which also needs to handle retries.

Examples:

  1) Highlevel
       downloadToBuffer should success:
     Error: connect ETIMEDOUT 52.165.136.32:443
      at new RestError (D:\a\1\s\sdk\core\core-http\lib\restError.ts:18:5)
      at AxiosHttpClient.<anonymous> (D:\a\1\s\sdk\core\core-http\lib\axiosHttpClient.ts:162:15)
      at step (D:\a\1\s\common\temp\node_modules\.registry.npmjs.org\tslib\1.10.0\node_modules\tslib\tslib.js:136:27)
      at Object.throw (D:\a\1\s\common\temp\node_modules\.registry.npmjs.org\tslib\1.10.0\node_modules\tslib\tslib.js:117:57)
      at rejected (D:\a\1\s\common\temp\node_modules\.registry.npmjs.org\tslib\1.10.0\node_modules\tslib\tslib.js:108:69)
      at processTicksAndRejections (internal/process/task_queues.js:82:5)
@mikeharder mikeharder added the EngSys This issue is impacting the engineering system. label Jul 8, 2019
@mikeharder mikeharder self-assigned this Jul 8, 2019
@HarshaNalluru
Copy link
Member

Created a new branch AvoidRetries out of feature/storage and removed the mocha retry functionality.

storage-queue tests succeeded.

Occasional failures in storage-blob tests -
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=63958&view=results
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=63952&view=results

@kurtzeborn kurtzeborn added Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files) and removed EngSys This issue is impacting the engineering system. labels Jul 23, 2019
@kurtzeborn
Copy link
Member

Assigning this to @HarshaNalluru and attaching it to the preview 3 release for storage.

@HarshaNalluru
Copy link
Member

@jiacfan @XiaoningLiu

Please remove the retry option in a branch for the tests and verify them by doing multiple runs to find the causes behind these transient issues.
Probably, need be handled on a case-to-case basis in a better way.
It is in our best interests to remove the retries and run the tests so that we may uncover any hidden bugs with the SDK or even the service.

@mikeharder mikeharder self-assigned this Jan 10, 2020
@mikeharder mikeharder added the EngSys This issue is impacting the engineering system. label Jan 10, 2020
@mikeharder
Copy link
Member Author

I am currently working to get all live tests passing at 90% (with no test-level retries). As part of this, we will need to disable retries in the JS tests and investigate the root causes.

@mikeharder
Copy link
Member Author

PR to revert retries: #6910

@jiacfan
Copy link
Member

jiacfan commented Aug 21, 2020

@ljian3377 ljian3377 added this to the Backlog milestone Oct 21, 2020
@mikeharder mikeharder removed their assignment Dec 1, 2020
@ramya-rao-a ramya-rao-a removed the EngSys This issue is impacting the engineering system. label Feb 1, 2021
@ramya-rao-a
Copy link
Contributor

It does not look like there is any pending work here.
The retries that were added have been removed.

Please post a comment if there is anything else to do here

@xirzec xirzec removed this from the Backlog milestone May 18, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

9 participants