Skip to content

Orancle ci fix#19099

Draft
stefans-elastic wants to merge 1 commit into
elastic:mainfrom
stefans-elastic:orancle-ci-fix
Draft

Orancle ci fix#19099
stefans-elastic wants to merge 1 commit into
elastic:mainfrom
stefans-elastic:orancle-ci-fix

Conversation

@stefans-elastic
Copy link
Copy Markdown
Contributor

Proposed commit message

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@github-actions github-actions Bot mentioned this pull request May 20, 2026
5 tasks
@github-actions
Copy link
Copy Markdown
Contributor

TL;DR

The Check integrations oracle Buildkite step is failing in build 43157, and the strongest signal points to a readiness-regression in the Oracle system-test config changes on commit 8cefec230c503a71ed08be67dfb6b74dbee9064a (PR branch stefans-elastic:orancle-ci-fix).

Remediation

  • Restore the removed agent.pre_start_script readiness gate in Oracle system test configs (at least packages/oracle/data_stream/*/_dev/test/system/test-*-config.yml) so tests wait for stable Oracle readiness before the agent starts.
  • Keep only one readiness strategy (either compose healthcheck gating or pre-start sqlplus probe), then re-run Check integrations oracle to confirm system tests pass.
Investigation details

Root Cause

This looks like a configuration/test-readiness regression introduced by the PR branch changes to Oracle dev test infrastructure:

  1. Buildkite fails the Oracle package step:

    • --- [oracle] failed
    • Error: The command exited with status 1
  2. The failing commit modifies only Oracle docker-compose readiness behavior across all data streams:

    • packages/oracle/data_stream/memory/_dev/deploy/docker/docker-compose.yml
    • packages/oracle/data_stream/performance/_dev/deploy/docker/docker-compose.yml
    • packages/oracle/data_stream/sysmetric/_dev/deploy/docker/docker-compose.yml
    • packages/oracle/data_stream/system_statistics/_dev/deploy/docker/docker-compose.yml
    • packages/oracle/data_stream/tablespace/_dev/deploy/docker/docker-compose.yml
  3. In the same branch history, Oracle system test configs had their readiness pre-start logic removed (the current main version still includes it), e.g.:

    • packages/oracle/data_stream/memory/_dev/test/system/test-memory-config.yml:40-88 on main contains a pre_start_script that performs exponential-backoff and requires consecutive successful Oracle probes before continuing.

Given the log is truncated to teardown/upload lines, this regression is the most concrete source-level explanation for an Oracle-only system failure in this PR.

Evidence

Verification

  • Not run locally in this workflow environment (no full failing test traceback available in the pre-fetched Buildkite log; only teardown + artifact upload tail was provided).

Follow-up

If you can share the full failing oracle-system-*.xml assertion/log snippet from this build’s artifacts, I can narrow this to the exact failing assertion and provide a one-file patch recommendation.

Note

🔒 Integrity filter blocked 4 items

The following items were blocked because they don't meet the GitHub integrity level.

  • #19099 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • Orancle ci fix #19099 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #19099 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #11801 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

@stefans-elastic stefans-elastic force-pushed the orancle-ci-fix branch 2 times, most recently from 02d3c1e to 00de5bc Compare May 22, 2026 11:45
@elasticmachine
Copy link
Copy Markdown

elasticmachine commented May 22, 2026

💔 Build Failed

Failed CI Steps

History

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants