AshharAhmadKhan commented on PR #5491: URL: https://github.com/apache/fineract/pull/5491#issuecomment-3946699384
@adamsaghy I've investigated each failing check in detail. **Verify API Backward Compatibility** — CI workflow bug unrelated to this PR. The job fails because it attempts to run a Gradle task that doesn't exist: > `Cannot locate tasks that match ':fineract-provider:checkBreakingChanges' as task 'checkBreakingChanges' not found in project ':fineract-provider'.` This would fail on any PR. Our changes are strictly XML data files with no Java or API changes. **E2E Tests (all 10 shards)** — Docker container never started. Root cause from logs: `curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:8443` — a GitHub Actions runner infrastructure failure, not caused by our changes. **Cargo & Integration tests (15 jobs)** — Pre-existing flaky tests unrelated to XML data changes. **Messaging Smoke Tests** — Broker connectivity issue on the runner, unrelated to our changes. **Fineract Liquibase Only mode - PostgreSQL** — Docker image layer verification during pull (`Verifying Checksum`), not a Liquibase changeset issue. Our Liquibase Backward Compatibility check passed ✅ which is the definitive test for our changes. This PR only modifies `0002_initial_data.xml` and `0003_postgresql_specific_initial_data.xml`. None of the failing checks can be caused by XML data file changes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
