Test branch package-spec#1189 - DO NOT MERGE

[elastic-vault-github-plugin-prod]

Update package-spec reference to elastic/package-spec@fa59ed1.
Automated by Buildkite build

Relates: elastic/package-spec#1189

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 906bdd1

Failed CI Steps

• Check integrations aws
• Check integrations cursor
• Check integrations google_scc
• Check integrations netbox
• Check integrations tenable_io

History

cc @teresaromero

[github-actions]

TL;DR

The four failed Buildkite steps (cursor, google_scc, netbox, tenable_io) cannot be traced to a concrete code/package-spec bug from the available logs: the prefetched logs only contain teardown/artifact-upload tails and omit the failing test output. I did not find evidence that package-spec PR 1189's profiling -> profiles enum change affects these packages.

Remediation

• Inspect the full Buildkite job logs or the uploaded xUnit artifacts for the exact failing suite/assertion, especially the *-system-*.xml files listed in the artifact upload output.
• If the full logs are unavailable, rerun the failed Buildkite steps with full log/artifact retention; no package code change is recommended from the currently available evidence.

Investigation details

Root Cause

Inconclusive from the accessible data. The PR only changes go.mod/go.sum to replace github.com/elastic/package-spec/v3 with the package-spec PR build. The upstream package-spec diff renames the data stream type enum value from profiling to profiles, but the failed packages' manifests all use type: logs or type: integration, and local validation did not reproduce a package-spec validation failure.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/44717
• Failed steps: Check integrations cursor, Check integrations google_scc, Check integrations netbox, Check integrations tenable_io
• Available log excerpt pattern from each prefetched file:

  --- [package] failed
  Error: The command exited with status 1
  user command error: exit status 1
  ~~~ Uploading artifacts
  

• The prefetched log files under /tmp/gh-aw/buildkite-logs/ are only 149 lines each and contain teardown plus artifact uploads, not the earlier failing assertion/error.
• PR changed files are limited to go.mod and go.sum; no package files were changed.
• Local search found no type: profiling or type: profiles in packages/cursor, packages/google_scc, packages/netbox, or packages/tenable_io.

Verification

• Built an elastic-package binary with the same temporary replace github.com/elastic/package-spec/v3 => github.com/teresaromero/package-spec/v3 v3.0.0-20260618081520-fa59ed1aaf19 override.
• Ran elastic-package -C packages/{cursor,google_scc,netbox,tenable_io} check; all four package checks passed.
• Ran elastic-package test static for all four packages; all passed.
• Asset/pipeline/policy/system tests could not be reproduced in this agent because Docker is unavailable here; Buildkite did run with a stack, so its full job log or xUnit artifacts are needed for the failing assertion.

Follow-up

If the full artifacts show a repeated system-test assertion, use that assertion to classify it as a package test failure; if they show stack/client/service errors, classify it as infrastructure and retry the four failed package steps.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• buildkiteassets.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "buildkiteassets.com"

See Network Configuration for more information.

---

What is this? | From workflow: PR Buildkite Detective

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