Skips azure compat test to make #1979 compat tests non-flaky but we still need to fix the bug from #1979.
What does this implement or fix?
I've packaged up a few other improvements in this pr as well:
Skips the azure tests
Replaces the 4.5.0 version with a 4.5.1, this should allow us to run lmdb and mongo compat tests without segfaults.
Use shell=True and an abspath to successfully run on conda feedstock linux runners. This was tested to work in here, although for some reason still doesn't work on mac. We'll fix the mac issues later.
Also running 4.5.1 uncovered that the mongo segfault is not entirely fixed. Skipping mongo similarly to azure tests.
Any other comments?
Checklist
Checklist for code changes...
- [ ] Have you updated the relevant docstrings, documentation and copyright notice?
- [ ] Is this contribution tested against [all ArcticDB's features](../docs/mkdocs/docs/technical/contributing.md)?
- [ ] Do all exceptions introduced raise appropriate [error messages](https://docs.arcticdb.io/error_messages/)?
- [ ] Are API changes highlighted in the PR description?
- [ ] Is the PR labelled as enhancement or bug so it appears in autogenerated release notes?
Reference Issues/PRs
Skips azure compat test to make #1979 compat tests non-flaky but we still need to fix the bug from #1979.
What does this implement or fix?
I've packaged up a few other improvements in this pr as well:
shell=Trueand anabspathto successfully run on conda feedstock linux runners. This was tested to work in here, although for some reason still doesn't work on mac. We'll fix the mac issues later.Any other comments?
Checklist
Checklist for code changes...
- [ ] Have you updated the relevant docstrings, documentation and copyright notice? - [ ] Is this contribution tested against [all ArcticDB's features](../docs/mkdocs/docs/technical/contributing.md)? - [ ] Do all exceptions introduced raise appropriate [error messages](https://docs.arcticdb.io/error_messages/)? - [ ] Are API changes highlighted in the PR description? - [ ] Is the PR labelled as enhancement or bug so it appears in autogenerated release notes?