search

qdrant / vector-db-benchmark

Framework for benchmarking vector search engines
https://qdrant.tech/benchmarks/
Apache License 2.0
270 stars 77 forks source link

Allow CI to force clear previously running resources if required #182

Closed KShivendu closed 2 months ago

KShivendu commented 2 months ago

CI benches were failing. I found the following errors from the logs:

Error response from daemon: conflict: unable to remove repository reference "docker.io/qdrant/qdrant:master" (must force) - container 40054a4e5693 is using its referenced image 3d4537be4e7c

Error response from daemon: Conflict. The container name "/qdrant-continuous" is already in use by container "40054a4e5693eda6b6597fc6f247ad365c5be985a7d545e3084c34b994ebac68". You have to remove (or rename) that container to be able to reuse that name.

Also, on sshing into the machine I found that sometimes 2 vector-db-benchmark containers are running if the 1st workflow is cancelled. This isn't ideal for perf benchmarking and should be avoided.

So we should clear existing resources before running CI workflow.

KShivendu commented 2 months ago

It fixed the CI. The latest run with this branch was successful