-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Only one of azure key or token can be specified in 3rd party tests #54876
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
Conversation
Pinging @elastic/es-distributed (:Distributed/Snapshot/Restore) |
@elasticmachine run elasticsearch-ci/bwc |
@elasticmachine update branch |
@elasticmachine run elasticsearch-ci/bwc |
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.
LGTM, test failures seem unrelated
@elasticmachine run elasticsearch-ci/bwc |
1 similar comment
@elasticmachine run elasticsearch-ci/bwc |
@elasticmachine update branch |
Thanks Armin! |
#54803 introduces more QA tests for Azure storage service, but they fail the build is one of the key or token is missing. It should instead work like
repository-azure:qa
tests.