[Unit Tests] Fix lag after Unit Tests finish, fix flakiness in Sampling test #78
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.
Issue #, if available:
npm run testcommand stalls for 20s after all tests pass (or fail), discovered caused byConcurrencytest, likely due toexportTimeoutMillisdefault value being set inAwsBatchUnsampledSpanProcessortestSomeReservoirthat may fail when sampling targets are not refreshed in time for the unit tests (due to the test being reliant onsetTimeoutwhich doesn't guarantee exact time of execution).Description of changes:
exportTimeoutMillisvalue forAwsBatchUnsampledSpanProcessorconfig inConcurrencytesttestSomeReservoirto properly cleanup the fake clock, provide more time for Sampling targets to refresh on time for the unit test run.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.