Flaky test fix for StoringSubscriberTest

[Fred1155]

Motivation and Context

The stochastic_subscriberSeemsThreadSafe test in StoringSubscriberTest is flaky and gives

[ERROR]   StoringSubscriberTest.stochastic_subscriberSeemsThreadSafe:188 » Execution org.opentest4j.AssertionFailedError: 
expected: 0
 but was: 1

The reason seems to be that the onSubscribe() likely triggers an initial request(n) call, the Producer immediately starts sending messages (0, 1, 2...). However, consumer thread starts later and may miss message 0 .

Modifications

Start consumer first and then call the onSubscribe()

Testing

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.