mirror of
https://github.com/Stone-Red-Code/dvc.git
synced 2026-11-02 07:18:25 +01:00
Saugat Pachhai
788d840e7d
`Azure` tests are flaky for some reason. When I investigated one
of the job [1], something seemed wrong with the Azurite or
the client lib.
On `AzureTree.blob_service`, we do the following to check if the
container exists:
```python
try:
container_client.get_container_properties()
except ResourceNotFoundError:
container_client.create_container()
```
When looking at the test log, I found out that the
`get_container_properties` was failing with
`ErrorCode:ContainerNotFound` whereas `create_container`
successively was failing with `ErrorCode:ContainerAlreadyExists`.
`create_container` is correct, but `get_container_properties` is
incorrect, as many of the Azure tests have already run successfully
before.
So, either the Azurite has/had bug or the client lib has a bug.
Anyway, we'll find out after updating the Azurite.
[1]: https://github.com/iterative/dvc/runs/1448864706#step:7:4029
23 lines
530 B
YAML
23 lines
530 B
YAML
---
|
|
version: '3.2'
|
|
services:
|
|
azurite:
|
|
image: mcr.microsoft.com/azure-storage/azurite:3.9.0
|
|
ports:
|
|
- "10000"
|
|
oss:
|
|
image: rkuprieiev/oss-emulator
|
|
ports:
|
|
- "8880"
|
|
hdfs:
|
|
image: rkuprieiev/docker-hdfs
|
|
hostname: localhost
|
|
ports:
|
|
- "8020"
|
|
# NOTE: having this port as dynamic one will require modifying
|
|
# `dfs.datanode.address` in `hdfs-site.xml` and probably something
|
|
# else, so using default one for now.
|
|
- "50010:50010"
|
|
- "50075:50075"
|
|
- "50070"
|