Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix allure report creation on periodic pg_regress testing #10171

Merged
merged 4 commits into from
Dec 17, 2024

Conversation

a-masterov
Copy link
Contributor

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.

@a-masterov a-masterov requested a review from a team as a code owner December 17, 2024 16:26
@a-masterov a-masterov enabled auto-merge December 17, 2024 16:39
@a-masterov a-masterov disabled auto-merge December 17, 2024 16:40
Copy link

github-actions bot commented Dec 17, 2024

7121 tests run: 6823 passed, 0 failed, 298 skipped (full report)


Flaky tests (6)

Postgres 17

Postgres 15

Code coverage* (full report)

  • functions: 31.3% (8395 of 26788 functions)
  • lines: 48.0% (66620 of 138664 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
20668c6 at 2024-12-17T20:55:50.834Z :recycle:

@a-masterov a-masterov enabled auto-merge December 17, 2024 20:07
@a-masterov a-masterov added this pull request to the merge queue Dec 17, 2024
Merged via the queue into main with commit c52514a Dec 17, 2024
87 checks passed
@a-masterov a-masterov deleted the amasterov/fix-allure-report branch December 17, 2024 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants