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

potential stream response test fix #234

Merged
merged 4 commits into from
Oct 6, 2021
Merged

potential stream response test fix #234

merged 4 commits into from
Oct 6, 2021

Conversation

The-EDev
Copy link
Member

@The-EDev The-EDev commented Oct 5, 2021

The commit has a typo, the issue is 233, not 223

fixes #233

This will either fix the issue (223), be generally better than the previous way the test was conducted, or change the failure rate from 70% to 100%
@The-EDev The-EDev changed the title potential stream response fix potential stream response test fix Oct 5, 2021
@The-EDev
Copy link
Member Author

The-EDev commented Oct 5, 2021

I've just done 1 CI run and it compiled and tested fine, running 2 more

Update: 2 other times ran, everything seems to be in order, no failures.

@The-EDev The-EDev marked this pull request as ready for review October 5, 2021 12:58
tests/unittest.cpp Outdated Show resolved Hide resolved
tests/unittest.cpp Outdated Show resolved Hide resolved
tests/unittest.cpp Outdated Show resolved Hide resolved
Copy link
Collaborator

@luca-schlecker luca-schlecker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good. 👍

@The-EDev The-EDev merged commit 63dcfb0 into master Oct 6, 2021
@The-EDev The-EDev deleted the fix_stream_res branch October 6, 2021 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TEST_CASE("stream_response") doesn't work most of the time.
3 participants