-
Notifications
You must be signed in to change notification settings - Fork 701
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
Unit test client_multiple_requests_disconnects_handled is failed #842
Comments
Hello, @iroddis, can you describe the expected scenario of the |
I cannot reproduce the failure on my dev box (From right after PR #840 is merged). I built with g++ and clang++, both in "Release" mode and "Debug" mode, and ran all unit tests (all pass), plus my own app runs fine. All 4 builds are very noisy with compiler warnings (I'd love for those to be cleaned up some day), but all 4 "worked". hyperxor@, what is your build platform?
|
@dennisjenkins75 Ok, thank you, I will see.
|
@dennisjenkins75, try running via autopkgtest. There's notes on how to do this in the readme. It will build and run all unit and CI tests within a container so there are hopefully no side effects spilling in from your system affecting the results. |
@dennisjenkins75 @kiplingw I have found tbe same problem with tests here - arm64 build of pistache 0.0.002-202011242302~ubuntu20.04.1 in ubuntu focal RELEASE (link):
|
@dennisjenkins75 I will close this issue in you don't mind. Fix is working. |
Sadly it's still re-appearing in the unstable PPA builder as of today.
|
Failed again today for focal on amd64.
|
…bug_info #842: Add more debug traces to http server test
More again as of today here.
|
Again just now while testing @jacobbogdanov's #859, but this time locally:
|
Has anyone attempted to reproduce the problem under valgrind, specifically "helgrind" [1]? Or compile the code with TSAN [2] ? [1] https://valgrind.org/docs/manual/hg-manual.html |
I'll try to add support for the thread sanitizer (and also others) in a PR in the following hours |
I've ran the tests with the thread sanitizer (with both GCC and Clang) and it reports data races in 19 tests, specifically |
I don't know anything about either of the two tools Dennis recommended. But I would suggest that we eliminate false positives from the log to make things easier. |
@kiplingw Hello, can you send build fails (if any) on |
Will do. |
Fix issue #842 and small refactoring
@kiplingw I think this issue can be closed if there are no bug reproductions. |
Yep. While the Travis Clang pipeline is broken for no reason (they probably messed up the apt sources), GCC builds seem fine. Good job :) |
Yes indeed, well done. Hopefully it's been squashed for good and this doesn't resurrect itself. |
I swear this bug is cursed. Happening again on armhf. |
I faced this issue quite often. Thread sanitizer report:
|
Hello,
I have run unit tests on the latest souce and got the following error:
It seems it happened after this #838 pull request.
The text was updated successfully, but these errors were encountered: