build(deps): bump google.golang.org/grpc from 1.83.1 to 1.83.2 in /testing

[dependabot]

Bumps google.golang.org/grpc from 1.83.1 to 1.83.2.

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.83.2

Security

• server: Reject requests missing both :authority and Host headers with HTTP 400 and status Internal. (grpc/grpc-go#9365)
  • Special Thanks: @​winklemad

Commits

• 030ee8b Update version to 1.83.2 (#9375)
• 8668b69 cherry-pick #9365 to v1.83.x (#9366)
• a3e952d cherry-pick #9346 to v1.83.x and update x/net dependency (#9369)
• 58f8fd9 Change version to 1.83.2-dev (#9337)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[mergify]

This pull request does not have a backport label. Could you fix it @dependabot[bot]? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[github-actions]

TL;DR

The Buildkite failure is an e2e test failure in TestStandAloneRunningSuite/TestAgentGracefulForceUnenroll, not a compile/dependency resolution error. Based on the available logs and PR diff, this looks like a flaky/timing failure in the long-running unenroll flow rather than a regression from the grpc bump itself.

Remediation

• Re-run the Buildkite e2e step once to confirm whether this is transient.
• If it reproduces, inspect the uploaded build/test-e2e-linux.out.xml artifact for the exact failed assertion and then run TEST_RUN=TestStandAloneRunningSuite/TestAgentGracefulForceUnenroll mage test:e2e to localize which Eventually window is timing out.

Investigation details

Root Cause

The failing job reports only one subtest failure:

• TestStandAloneRunningSuite/TestAgentGracefulForceUnenroll failed after a long run (219.77s).

The PR changes only testing/go.mod and testing/go.sum (dependency version updates), with no direct changes to the unenroll e2e logic. The unenroll test itself has multiple time-bound Eventually checks and explicit notes about short race windows, which is consistent with intermittent timing failures under CI load:

• testing/e2e/stand_alone_test.go#L862-L884 (agent reaches online/updating)
• testing/e2e/stand_alone_test.go#L902-L923 (components become empty after policy change)
• testing/e2e/stand_alone_test.go#L933-L940 (UNENROLL log observed)

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/16718
• Job/step: E2E Test (.buildkite/scripts/e2e_test.sh)
• Key log excerpt:
  • --- FAIL: TestStandAloneRunningSuite (735.20s)
  • --- FAIL: TestStandAloneRunningSuite/TestAgentGracefulForceUnenroll (219.77s)
  • FAIL github.com/elastic/fleet-server/testing/e2e 1474.104s

Additional signal:

• No detective comment was already present on this PR (only an existing mergify backport-label reminder).
• No open flaky-test issue directly matched TestAgentGracefulForceUnenroll from accessible issue data.

Verification

• Not run in this environment (Docker-in-Docker unsupported here for local e2e reproduction).

Follow-up

If this keeps reproducing after retry, capture the exact assertion text from build/test-e2e-linux.out.xml and file/associate a flaky-test issue for TestAgentGracefulForceUnenroll with that assertion and timing context.

---

What is this? | From workflow: PR Buildkite Detective

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