-
Notifications
You must be signed in to change notification settings - Fork 3
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
google_pipeline_tests falls in deadlock #3
Comments
Hi, It might be worthwhile to raise this issue on the boost mailing list if
Thanks, On Oct 26, 2016 12:09, "Adam Oleksy" [email protected] wrote: Hi, Sometimes it prints out also: I've built this test with boost 1.58 on ubuntu 16.04.1 with gcc 5.4.0. — |
Hi Benedek, |
Hi,
I would like to use your library in my project. Unfortunately I've (probably) found a bug.
I've compiled google_pipeline_tests, and run it in a loop. In most cases it ends as expected, but sometimes it hangs. The output is as following:
Running 3 test cases...
get for 2
get for 4
get for 6
get for 8
get for 10
Consuming user (User : 2)
Consuming user (User : 4)
Consuming user (User : 6)
Consuming user (User : 8)
Consuming user (User : 10)
find_uid for Foo
find_uid for BarA
find_uid for BazBB
find_uid for QuxCCC
get for 3
get for 3
get for 4
get for 4
get for 5
get for 5
get for 6
get for 6
Consuming user (User : 3)
Consuming user (User : 3)
Consuming user (User : 4)
Consuming user (User : 4)
Consuming user (User : 5)
Consuming user (User : 5)
Consuming user (User : 6)
Consuming user (User : 6)
Sometimes it prints out also:
a.out: /usr/include/boost/thread/pthread/condition_variable_fwd.hpp:81: boost::condition_variable::~condition_variable(): Assertion `!ret' failed.
unknown location(0): fatal error in "Example": signal: SIGABRT (application abort requested)
I've built this test with boost 1.58 on ubuntu 16.04.1 with gcc 5.4.0.
Have you faced such problem?
If you want I can provide more information, e.g. backtraces.
The text was updated successfully, but these errors were encountered: