There seem to be a couple of issues with the get-driver-status utility when following the readme.
1) Trying to run pip install --no-cache-dir -r requirements.txt is failing with
The conflict is caused by:
The user requested async-timeout==3.0.1
aiohttp 3.8.5 depends on async-timeout<5.0 and >=4.0.0a3
This seems to have been the result of upgrading to aiohttp 3.8.5. Reverting the version back to 3.7.4 from the previous version of requirements.txt resolves the issue but is probably not the right solution.
2) Trying to build the docker version using docker build -f Dockerfile -t get-driver-status . is failing due to a Cython issue. A workaround is documented here and requires constraining Cython<3 when pyaml pulls it in as a dependency.
I am trying to understand why these wouldn't have caused a CI pipeline failure as this utility is used to workout which DID tests to run I thought ?
There seem to be a couple of issues with the get-driver-status utility when following the readme.
1) Trying to run
pip install --no-cache-dir -r requirements.txtis failing withThis seems to have been the result of upgrading to aiohttp 3.8.5. Reverting the version back to 3.7.4 from the previous version of requirements.txt resolves the issue but is probably not the right solution.
2) Trying to build the docker version using
docker build -f Dockerfile -t get-driver-status .is failing due to a Cython issue. A workaround is documented here and requires constraining Cython<3 when pyaml pulls it in as a dependency.I am trying to understand why these wouldn't have caused a CI pipeline failure as this utility is used to workout which DID tests to run I thought ?