Hello Cloudberry developers,
I wanted to provide an update on our GitHub Workflow CI environment and
testing infrastructure. You can view our latest main merge workflow run
here: https://github.com/apache/cloudberry/actions/runs/12133736336
We are currently running all CI operations within the GitHub hosted runner
environment, with no external resource dependencies. Our workflow covers
both PR submissions and main branch merges. We are utilizing a workflow
matrix approach to define individual test configurations, enabling parallel
execution and clear separation of test scenarios.
Build Environment Details: Our build environment has been configured to
ensure consistent and reproducible builds:
- Platform: Rocky Linux 9
- Build Process:
- Separate configure and build steps
- RPM package generation for testing, which is subsequently used for
all test phases
Test Configuration: We maintain a comprehensive test suite that exercises
various aspects of the system. Currently, we are executing the following
test schedules (with more being added regularly):
- ic-good-opt-off: Basic functionality testing without ORCA
- ic-expandshrink: Tests focusing on cluster expansion and contraction
- ic-singlenode_regress: Core regression tests in single-node
configuration
- ic-singlenode_isolation: Isolation testing for component interactions
- ic-singlenode_isolation2: Extended isolation test scenarios
- ic_resgroup-v2: Resource group management testing
Test Results Processing: Our test results analysis has been streamlined for
quick identification of issues:
- Automated analysis of test results provides immediate feedback
- Failed test suites are clearly highlighted in the workflow output
- Regression diffs are available for review through the Check and
Display Regression Diffs feature, making it easy to identify changes in
behavior:
The workflow summary provides detailed information for each run:
- Complete build configuration information, including compiler settings
and dependencies
- RPM package details with version information and included components
- Test configuration results broken down by matrix configuration
- Number of tests passed
- Number of tests failed
- Number of tests ignored
- Specific test suites that failed (if any)
- Specific test suites that were ignored (if any)
Available Artifacts: Each workflow run produces several artifacts for
detailed analysis:
1. Development RPM for Rocky 9
2. Build logs containing compilation details and warnings
3. Installation logs for tracking deployment issues
4. Test schedule logs with detailed test execution information
5. Test regression logs showing behavioral changes and demo cluster data
directories
Please review the latest workflow run for detailed metrics and testing
outcomes. If you have any questions or suggestions for improving our CI
process, feel free to respond to this thread.
-=e
--
Ed Espino
Apache Cloudberry (incubating) & MADlib
