Repository navigation
Conversation
The Behave workflow built and tested on Rocky Linux 9 only. gpMgmt is
Python and shell, so many of its problems depend on the OS: the Python
version, ssh and rsync behavior, and system packages. Rocky 8 ships
Python 3.6 and Rocky 10 ships Python 3.12, so neither is covered today.
Build one RPM per OS, and run every selected suite on every selected
OS. A full run is now 3 builds and 51 Behave jobs. The job and
artifact names carry the OS, so the three OSes do not overwrite each
other's results. A new os_selection input lets a manual run pick the
OSes, the same way test_selection picks the suites.
If the build for one OS fails, the suites for the other OSes still
run. Only the suites of the failed OS fail, at the artifact download.
The build job is renamed to "Build Behave RPM (<os>)". .asf.yaml
requires a check named "Build Apache Cloudberry RPM", and that check
belongs to build-cloudberry.yml, not to this workflow.
Two problems stopped the workflow from working on Rocky 10:
* The RPM file name took one digit of VERSION_ID, so Rocky 10 ("10.0")
gave "el1" and the copy failed. Take all the leading digits.
* The RPM install used --releasever=9 for every OS. Take the release
from the OS name.
Assisted-by: Claude Code
Member
Author
|
Will rebase on #2230. |
This file contains hidden or 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
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.
The Behave workflow built and tested on Rocky Linux 9 only. gpMgmt is Python and shell, so many of its problems depend on the OS: the Python version, ssh and rsync behavior, and system packages. Rocky 8 ships Python 3.6 and Rocky 10 ships Python 3.12, so neither is covered today.
Build one RPM per OS, and run every selected suite on every selected OS. A full run is now 3 builds and 51 Behave jobs. The job and artifact names carry the OS, so the three OSes do not overwrite each other's results. A new os_selection input lets a manual run pick the OSes, the same way test_selection picks the suites.
If the build for one OS fails, the suites for the other OSes still run. Only the suites of the failed OS fail, at the artifact download.
The build job is renamed to "Build Behave RPM ()". .asf.yaml requires a check named "Build Apache Cloudberry RPM", and that check belongs to build-cloudberry.yml, not to this workflow.
Two problems stopped the workflow from working on Rocky 10:
Assisted-by: Claude Code
Fixes #ISSUE_Number
What does this PR do?
Type of Change
Breaking Changes
Test Plan
make installcheckmake -C src/test installcheck-cbdb-parallelImpact
Performance:
User-facing changes:
Dependencies:
Checklist
Additional Context
CI Skip Instructions