You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#### Reference Issues/PRs
<!--Example: Fixes#1234. See also #3456.-->
#### What does this implement or fix?
Successful execution 5.2.6:
https://github.com/man-group/ArcticDB/actions/runs/14641126753/job/41083591802
5.1.2: https://github.com/man-group/ArcticDB/actions/runs/14637571996
4.5.1:
https://github.com/man-group/ArcticDB/actions/runs/14639124835/job/41077126258
1.6.2:
https://github.com/man-group/ArcticDB/actions/runs/14701046721/job/41250511273
The PR contains workflow definition to execute tests on installed
arcticdb it is combination of approaches:
#2330#2316
Installation tests are now in separate folder
(python/installation_tests) not part of tests. They have their own
fixtures, making them independent from rest of code base
The tests are direct copy from originals with one modified to user ver 2
API. Otherwise now if there are changes in API each test in installation
set can be addapted. As tests run very fast no need to use simulators,
instead directly using S3 real storage
The tests are executed by a workflow.
Currently each test is executed against LMDB and real S3. The moto
simulated version is not available in this moment due to tight coupling
with protobufs which differ for ach version as well as tight coupling
with whole existing test code.
The workflow have 2 triggers:
- manual trigger - allowing tests to be executed manually on demand
- on schedule - the schedule execution is overnight. Each arcticdb
version tests are executed within 1hr difference from the other. Thats
is due to fact that executing all at once is likely to generate errors
with real storages
#### Any other comments?
#### Checklist
<details>
<summary>
Checklist for code changes...
</summary>
- [ ] 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?
</details>
<!--
Thanks for contributing a Pull Request to ArcticDB! Please ensure you
have taken a look at:
- ArcticDB's Code of Conduct:
https://github.com/man-group/ArcticDB/blob/master/CODE_OF_CONDUCT.md
- ArcticDB's Contribution Licensing:
https://github.com/man-group/ArcticDB/blob/master/docs/mkdocs/docs/technical/contributing.md#contribution-licensing
-->
---------
Co-authored-by: Georgi Rusev <Georgi Rusev>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
0 commit comments