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

Add delay in the delete test verification to work around service delete cache #23313

Merged
merged 1 commit into from
Aug 3, 2021

Conversation

pallavit
Copy link
Contributor

@pallavit pallavit commented Aug 3, 2021

This is the last ditch effort at making the pipeline green. If this does not work, I will go ahead and remove the verification and do the status code check instead.

@pallavit pallavit self-assigned this Aug 3, 2021
Copy link
Member

@alzimmermsft alzimmermsft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the service provide any hints on how long the back-off should be when you run into an error like this?

@alzimmermsft
Copy link
Member

/azp run java - containerregistry - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pallavit
Copy link
Contributor Author

pallavit commented Aug 3, 2021

Does the service provide any hints on how long the back-off should be when you run into an error like this?

The service actually tried removing the need for cache, which currently works for everything except delete. So, no there is no clear guidance here. I will talk to the service team and share a repro. We are seeing this across all languages too.

@pallavit pallavit merged commit 566badb into Azure:main Aug 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants