merge queue: checking #4006 on main (e3d4e05)

[mergify]

⏳ The pull request #4006 is queued for merge and currently being checked. ⏳

#4006 is queued for merge on branch main (e3d4e05).

This pull request has been created by Mergify to check the mergeability of #4006.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

• check-success=buildkite/elastic-package
• any of [🛡 GitHub branch protection]:
  • check-neutral = buildkite/elastic-package
  • check-skipped = buildkite/elastic-package
  • check-success = buildkite/elastic-package
• github-review-approved [🛡 GitHub branch protection]
  • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• github-review-approved [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• github-review-approved [🛡 GitHub repository ruleset rule [org] Require a PR]
  • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• any of [🛡 GitHub branch protection]:
  • check-success = CLA
  • check-neutral = CLA
  • check-skipped = CLA

Required conditions to stay in the queue:

• author~=^dependabot(|-preview)\[bot\]$
  • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• base=main
  • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• check-success=CLA
  • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• check-success=buildkite/elastic-package
  • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• github-review-approved [🛡 GitHub branch protection]
  • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• github-review-approved [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• github-review-approved [🛡 GitHub repository ruleset rule [org] Require a PR]
  • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• any of [🛡 GitHub branch protection]:
  • check-success = CLA
    • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
  • check-neutral = CLA
    • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
  • check-skipped = CLA
    • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
• any of [🛡 GitHub branch protection]:
  • check-success = buildkite/elastic-package
    • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
  • check-neutral = buildkite/elastic-package
    • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006
  • check-skipped = buildkite/elastic-package
    • Chore(deps): bump github.com/ProtonMail/go-crypto from 1.5.0 to 1.5.2 #4006

---
checking_base_sha: e3d4e05a3104082d5461a0ac5e9209e17414e91a
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 4006
    scopes: []
scopes: []
...

[infra-vault-gh-plugin-prod]

💔 Build Failed

• Buildkite Build
• Commit: 3703bdd

Failed CI Steps

• :go: Integration test: stack-command-7x
• :go: Integration test: mongodb

History

[github-actions]

TL;DR

The :go: Integration test: mongodb Buildkite step failed, but the captured job log only shows teardown and the wrapper exit path, not the underlying failing test/assertion. Given the PR diff only bumps github.com/ProtonMail/go-crypto in go.mod/go.sum, this looks non-actionable as a code regression in this PR and needs one more data point (full failing test stdout/stderr) to pinpoint root cause.

Remediation

• Re-run the failing Buildkite step and capture the full elastic-package test -C test/packages/parallel/mongodb -v output (or publish the uploaded build/test-results/mongodb-*.xml artifacts content in the job log).
• If rerun passes, treat this as transient CI/test flakiness; if rerun fails again, use the first failing test name/error from the full output to patch the failing package/test path directly.

Investigation details

Root Cause

The job exited through wrapper scripts after make returned non-zero, but the available log does not contain the original failing command output:

• .buildkite/scripts/integration_tests.sh:175-176 runs make ... test-check-packages-parallel and captures its exit code.
• .buildkite/scripts/integration_tests.sh:183-185 exits when that code is non-zero.
• scripts/test-check-packages.sh:15-65 installs an EXIT trap and runs cleanup, which is exactly what the provided log mostly contains.
• Makefile:128 maps test-check-packages-parallel to scripts/test-check-packages.sh.

PR scope check: pull_request_read(get_files) shows only go.mod and go.sum changed (dependency bump github.com/ProtonMail/go-crypto v1.5.0 -> v1.5.2), with no mongodb package/test code changes in this merge-queue PR.

Evidence

• Build: https://buildkite.com/elastic/elastic-package/builds/8847
• Job/step: :go: Integration test: mongodb
• Key log excerpt (/tmp/gh-aw/buildkite-logs/elastic-package-go-integration-test-mongodb.txt):
  • L85: + exit 1
  • L87: make: *** [Makefile:128: test-check-packages-parallel] Error 1
  • L113: make SERVERLESS=false PACKAGE_UNDER_TEST=mongodb test-check-packages-parallel failed with 2
  • L116-L118: command exited with status 2
• No open flaky-test issue matched mongodb in this repository at investigation time.

Verification

• Not run locally: this environment does not support Docker-in-Docker, so the integration stack test cannot be reproduced here.

Follow-up

• If the rerun fails with the same test signature, please share the failing test block (or artifact XML body) and I can map it to the exact source line-level fix.

---

What is this? | From workflow: Observability Agentic Workflow — Status

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