Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix allure report creation on periodic
pg_regress
testing (#10171)
## Problem The allure report finishes with the error `HttpError: Resource not accessible by integration` while running the `pg_regress` test against a cloud staging project due to a lack of permissions. ## Summary of changes The permissions are added.
- Loading branch information
c52514a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
6600 tests run: 6310 passed, 1 failed, 289 skipped (full report)
Failures on Postgres 16
test_storage_controller_many_tenants[github-actions-selfhosted]
: release-x86-64Flaky tests (6)
Postgres 17
test_create_churn_during_restart
: debug-x86-64test_wal_restore_http[True]
: release-x86-64Postgres 16
test_physical_replication_config_mismatch_max_locks_per_transaction
: release-arm64Postgres 15
test_pgdata_import_smoke[None-1024-RelBlockSize.MULTIPLE_RELATION_SEGMENTS]
: release-arm64Postgres 14
test_pgdata_import_smoke[None-1024-RelBlockSize.MULTIPLE_RELATION_SEGMENTS]
: release-arm64test_physical_replication_config_mismatch_max_locks_per_transaction
: release-x86-64Code coverage* (full report)
functions
:31.3% (8394 of 26820 functions)
lines
:48.0% (66632 of 138916 lines)
* collected from Rust tests only
c52514a at 2024-12-17T23:20:52.538Z :recycle: