GD-42: Fix test run stops at some point #43
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Why The test runs stops after 7 test-suites are executed and stuck with an error at await signal ExecutionCompleted # What Its unclear what the root cause is, it looks like the signal connection list of the executor is cleaned for some reasons. Added just a "hack" by fetching the signal list on each test-suite run
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
The test runs stops after 7 test-suites are executed and stuck with an error at await signal ExecutionCompleted
What
Its unclear what the root cause is, it looks like the signal connection list of the executor is cleaned for some reasons. Added just a "hack" by fetching the signal list on each test-suite run
pushed new gdUnit4.api version
<PackageReference Include="gdUnit4.api" Version="4.2.0-rc.202402222030" />