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

test_retriever.py::test_dpr_embedding for Weaviate is flaky #3024

Closed
bogdankostic opened this issue Aug 11, 2022 · 1 comment · Fixed by #3026
Closed

test_retriever.py::test_dpr_embedding for Weaviate is flaky #3024

bogdankostic opened this issue Aug 11, 2022 · 1 comment · Fixed by #3026
Labels
topic:tests type:bug Something isn't working

Comments

@bogdankostic
Copy link
Contributor

Describe the bug
This CI run failed due to Weaviate complaining that the used index is read-only. Therefore, writing documents and deleting the index resulted in an error. However, re-running the workflow resulted in all tests passing. We should make sure that the tests do not fail occasionally for no reason.

Error message

weaviate.exceptions.UnexpectedStatusCodeException: Add property to class! Unexpected status code: 422, with response body: {'error': [{'message': 'add property to shard "yR58cqXtj7Gq": store is read-only'}]}
weaviate.exceptions.UnexpectedStatusCodeException: Delete class from schema! Unexpected status code: 400, with response body: {'error': [{'message': "delete idx for class 'HaystackTest': drop index haystacktest: delete shard haystacktest_yR58cqXtj7Gq: store is read-only"}]}
@sjrl
Copy link
Contributor

sjrl commented Aug 11, 2022

Hey @bogdankostic this is blocking my PR #2856 and it failed again after trying to rerun just the failed job. Is there a recommendation for how to work around this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic:tests type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants