Skip to content

chore(deps): bump golang.org/x/tools from 0.49.0 to 0.50.0 - #21238

Merged
mrodm merged 1 commit into
mainfrom
dependabot/go_modules/golang.org/x/tools-0.50.0
Sep 15, 2026
Merged

mrodm merged 1 commit into
mainfrom
dependabot/go_modules/golang.org/x/tools-0.50.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 14, 2026 •

Copy link
Copy Markdown
Contributor

Bumps golang.org/x/tools from 0.49.0 to 0.50.0.

Commits
  • 265dd1a go.mod: update golang.org/x dependencies
  • 2af88d6 gopls/internal/cache: handle multiple legacy build constraints in standalone ...
  • 9e18529 gopls/internal/test/integration/fake: don't poll after a workspace edit
  • 2543006 go/gcexportdata: update package docs + minor tweaks
  • 7c2cac4 gopls/internal/golang/completion: handle new(expr)
  • 28649ea go/analysis/passes/modernize: elide redundant clone in appendclipped
  • 332fd4c gopls/internal/protocol: trace error messages
  • 4d65dec gopls/internal/cache: tolerate missing nodes in reachability analysis
  • 664b13f internal/refactor/inline: guard against non-ellipsis
  • 567ef61 go/analysis/passes/modernize: testingcontext - skip deferred calls
  • Additional commits viewable in compare view

@dependabot
dependabot Bot requested a review from a team as a code owner September 14, 2026 13:37
@github-actions

This comment has been minimized.

Bumps [golang.org/x/tools](https://github.com/golang/tools) from 0.49.0 to 0.50.0.
- [Release notes](https://github.com/golang/tools/releases)
- [Commits](golang/tools@v0.49.0...v0.50.0)

---
updated-dependencies:
- dependency-name: golang.org/x/tools
  dependency-version: 0.50.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/go_modules/golang.org/x/tools-0.50.0 branch from b89e24e to 9965b4d Compare September 14, 2026 14:22
@infra-vault-gh-plugin-prod

infra-vault-gh-plugin-prod Bot commented Sep 14, 2026 •

Copy link
Copy Markdown

⏳ Build in-progress, with failures

Failed CI Steps

History

@github-actions

This comment has been minimized.

@github-actions

Copy link
Copy Markdown
Contributor

TL;DR

The failing Buildkite step is blocked before tests execute because the expected Elastic Cloud deployment is missing (No Elastic Cloud deployment is registered ...), so this is an infrastructure/configuration failure, not a regression from this PR’s go.mod/go.sum bump.

Remediation

  • Recreate/register the expected deployment name (bk-stateful-ftr-2520-5ecea53f41b0) in the OOM test environment, then re-run Run FTR OOM tests.
  • If this recurs, harden the pipeline’s pre-flight checks to fail earlier with deployment provisioning diagnostics (or auto-provision) before invoking qaf kibana ftr run-config.
Investigation details

Root Cause

The step exits during environment setup for the external OOM FTR pipeline, before any package test assertions or repository code paths in this PR are exercised.

The command run is:

  • qaf kibana ftr run-config x-pack/solutions/security/test/security_solution_api_integration/test_suites/detections_response/rules_management/prebuilt_rules/oom_testing/configs/ess_basic_license.config.ts

It fails immediately with:

  • No Elastic Cloud deployment is registered with the name 'bk-stateful-ftr-2520-5ecea53f41b0'

This indicates missing test infrastructure state (deployment registration), not a code/type/test logic failure in elastic/integrations.

Evidence

  • Build: https://buildkite.com/elastic/integrations/builds/49608
  • Job/step: Run FTR OOM tests (package version: 9.5.5, EPR: (bkstatefulftr2520epr1eaca630bc7f.eproom.estc.dev/redacted))
  • Key log excerpts:
    • /tmp/gh-aw/buildkite-logs/appex-qa-stateful-security-prebuilt-rules-ftr-oom-testing-test_tube-run-ftr-oom-tests-package-version-955-epr-httpsbk.txt:136 (qaf kibana ftr run-config ...)
    • /tmp/gh-aw/buildkite-logs/appex-qa-stateful-security-prebuilt-rules-ftr-oom-testing-test_tube-run-ftr-oom-tests-package-version-955-epr-httpsbk.txt:141 (No Elastic Cloud deployment is registered ...)
  • PR change scope: dependency-only updates in go.mod and go.sum.

Verification

  • Not run locally: this failure depends on external Buildkite/Elastic Cloud environment provisioning.

Follow-up

  • If the deployment exists but name resolution is stale, check the pipeline variable/source generating bk-stateful-ftr-2520-5ecea53f41b0 for drift versus the actual created deployment identifier.

What is this? | From workflow: PR Buildkite Detective

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

@mrodm
mrodm merged commit 0f8e975 into main Sep 15, 2026
7 of 8 checks passed
@mrodm
mrodm deleted the dependabot/go_modules/golang.org/x/tools-0.50.0 branch September 15, 2026 08:09
@github-actions github-actions Bot mentioned this pull request Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant