CI(regress-tests): run less regression tests #8561
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bayandin
requested review from
a team,
knizhnik and
skyzh
and removed request for
a team
koivunej
approved these changes
Jul 31, 2024
arpad-m
approved these changes
Jul 31, 2024
koivunej
approved these changes
Jul 31, 2024
bayandin
changed the title
2100 tests run: 2033 passed, 0 failed, 67 skipped (full report)Code coverage* (full report)
* collected from Rust tests only The comment gets automatically updated with the latest test results
d2ce1c1 at 2024-07-31T13:07:46.696Z :recycle: |
bayandin
force-pushed
the
bayandin/run-less-regress-tests
branch
from
544240b
to
b206788
Compare
bayandin
force-pushed
the
bayandin/run-less-regress-tests
branch
from
b206788
to
d2ce1c1
Compare
arpad-m
pushed a commit
that referenced
this pull request
Aug 5, 2024
## Problem We run regression tests on `release` & `debug` builds for each of the three supported Postgres versions (6 in total). With upcoming ARM support and Postgres 17, the number of jobs will jump to 16, which is a lot. See the internal discussion here: https://neondb.slack.com/archives/C033A2WE6BZ/p1722365908404329 ## Summary of changes - Run `regress-tests` job in debug builds only with the latest Postgres version - Do not do `debug` builds on release branches
5 tasks
bayandin
added a commit
that referenced
this pull request
Aug 30, 2024
## Problem `promote-compatibility-data` job got broken and slightly outdated after - #8552 -- we don't upload artifacts for ARM64 - #8561 -- we don't prepare `debug` artifacts in the release branch anymore ## Summary of changes - Promote artifacts from release PRs to the latest version (but do it from `release` branch) - Upload artifacts for both X64 and ARM64
bayandin
added a commit
that referenced
this pull request
Sep 17, 2024
## Problem We've got 2 non-blocking failures on the release pipeline: - `promote-compatibility-data` job got skipped _presumably_ because one of the dependencies of `deploy` job (`push-to-acr-dev`) got skipped (#8940) - `coverage-report` job fails because we don't build debug artifacts in the release branch (#8561) ## Summary of changes - Always run `push-to-acr-dev` / `push-to-acr-prod` jobs, but add `skip_if` parameter to the reusable workflow, which can skip the job internally, without skipping externally - Do not run `coverage-report` on release branches
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
We run regression tests on
release&debugbuilds for each of the three supported Postgres versions (6 in total).With upcoming ARM support and Postgres 17, the number of jobs will jump to 16, which is a lot.
See internal discussion here: https://neondb.slack.com/archives/C033A2WE6BZ/p1722365908404329
Summary of changes
regress-testsjob in debug builds only with the latest Postgres versiondebugbuild on release branchesChecklist before requesting a review
Checklist before merging