Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: acquire lock before checking pendingRequests in controller test #42096

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

kruskall
Copy link
Member

Proposed commit message

fix race condition in TestQueueProducerBlocksUntilOutputIsSet

controller.queueProducer will modify pendingRequests so we need to acquire a lock before checking the slice

data race:

==================
WARNING: DATA RACE
Write at 0x00c0002b02a8 by goroutine 39:
  github.com/elastic/beats/v7/libbeat/publisher/pipeline.(*outputController).queueProducer()
      github.com/elastic/beats/v7/libbeat/publisher/pipeline/controller.go:237 +0x304
  github.com/elastic/beats/v7/libbeat/publisher/pipeline.TestQueueProducerBlocksUntilOutputIsSet.func1()
      github.com/elastic/beats/v7/libbeat/publisher/pipeline/controller_test.go:229 +0x35

Previous read at 0x00c0002b02a8 by goroutine 30:
  github.com/elastic/beats/v7/libbeat/publisher/pipeline.TestQueueProducerBlocksUntilOutputIsSet.func2()
      github.com/elastic/beats/v7/libbeat/publisher/pipeline/controller_test.go:236 +0x38
  github.com/elastic/beats/v7/libbeat/publisher/pipeline.waitUntilTrue()
      github.com/elastic/beats/v7/libbeat/publisher/pipeline/testing.go:178 +0x76
  github.com/elastic/beats/v7/libbeat/publisher/pipeline.TestQueueProducerBlocksUntilOutputIsSet()
      github.com/elastic/beats/v7/libbeat/publisher/pipeline/controller_test.go:233 +0x426
  testing.tRunner()
      testing/testing.go:1690 +0x226
  testing.(*T).Run.gowrap1()
      testing/testing.go:1743 +0x44

Goroutine 39 (running) created at:
  github.com/elastic/beats/v7/libbeat/publisher/pipeline.TestQueueProducerBlocksUntilOutputIsSet()
      github.com/elastic/beats/v7/libbeat/publisher/pipeline/controller_test.go:228 +0x2f1
  testing.tRunner()
      testing/testing.go:1690 +0x226
  testing.(*T).Run.gowrap1()
      testing/testing.go:1743 +0x44

Goroutine 30 (running) created at:
  testing.(*T).Run()
      testing/testing.go:1743 +0x825
  testing.runTests.func1()
      testing/testing.go:2168 +0x85
  testing.tRunner()
      testing/testing.go:1690 +0x226
  testing.runTests()
      testing/testing.go:2166 +0x8be
  testing.(*M).Run()
      testing/testing.go:2034 +0xf17
  main.main()
      _testmain.go:81 +0x164
==================
--- FAIL: TestQueueProducerBlocksUntilOutputIsSet (0.02s)
    testing.go:1399: race detected during execution of test

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

fix race condition in TestQueueProducerBlocksUntilOutputIsSet
@kruskall kruskall requested a review from a team as a code owner December 17, 2024 21:21
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Dec 17, 2024
@botelastic
Copy link

botelastic bot commented Dec 17, 2024

This pull request doesn't have a Team:<team> label.

Copy link
Contributor

mergify bot commented Dec 17, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kruskall? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit

Copy link
Contributor

mergify bot commented Dec 17, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify enhancement needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant