PG Integration tests and linter local dev improvements #1551
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.
PG Integration tests improvements:
pg_remote_backup_without_files_metadata_test
. Add to CI.make pg_clean
.Dockerfile_prefix
. Continue optimisation from [PG] Optimize docker-compose & dockerfiles for postgresql docker tests #1510.pg_pgbackrest_backup_fetch_test
andpg_ssh_backup_test
are excluded from running in one container because of special requirements. Makefile runs them in another docker-compose calls.pg_pgbackrest_backup_fetch_test
from 1000 to 60 seconds. I don't know much about test logic. But anyway running a data creation in test for 16 minutes looks overkill.After improvements all tests successfully runs on notebook. It took 30 minutes with Colima as a Docker runtime. Configuration is 2 CPU / 8 GB Memory.
Linter improvements: