Reduce timeout for unit tests #1907
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the issue
The
TestConcurrentLinePoolAccess
test is flaky and can get into a situation where the test will never finish.https://github.com/aws/amazon-cloudwatch-agent/actions/runs/18573122156/job/52952299604?pr=1903
This makes it so that when the unit tests are run, they use the full timeout set (15 minutes). The unit tests take an average of <5 minutes.
Description of changes
Reducing the unit test run timeout to 10 minutes. Fixed
TestConcurrentLinePoolAccess
by ensuring that the consumer channel is always closed even if the producer times out.License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Ran unit tests.
Requirements
Before commiting your code, please do the following steps.
make fmt
andmake fmt-sh
make lint
Integration Tests
To run integration tests against this PR, add the
ready for testing
label.