Running backup tests only in a cluster setup #385
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backup tests will be skipped for single server
Note
Low Risk
Primarily test gating plus static-analysis/dependency bumps; low runtime risk aside from potentially reduced CI coverage for backup APIs in non-cluster or older versions.
Overview
Backup integration coverage is narrowed:
test_backup_managementnow skips on non-cluster setups and on ArangoDB versions older than3.12.0(using the existingdb_versionfixture).Tooling/deps are tightened to align with newer typing/JWT libraries:
mypyis bumped to1.15.0(pre-commit anddevextra),PyJWTis constrained to>=2.10.0, mypy config disableswarn_unused_ignores, and JWT decode calls add# type: ignore[arg-type]to satisfy updated type checking.Written by Cursor Bugbot for commit 41ab3dd. This will update automatically on new commits. Configure here.