open_posix_testsuite: fix pthread_cond_destroy test error. #1097
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
According to the description of the pthread_cond_destroy function in glibc 2.32, it is advised to ensure that all threads blocked on the condition variable have been successfully awakened before calling this function, otherwise unpredictable situations may occur. In the glibc 2.32 version, this testcase will hang. Therefore, it is necessary to ensure that all threads have been successfully awakened before calling pthread_cond_destroy to destroy the condition variable. Signed-off-by: tanqinyun.tqy <tanqinyun.tqy@alibaba-inc.com>
|
The logs below indicate a failure in the test. ./interfaces/pthread_cond_destroy/pthread_cond_destroy_2-1.run-test[14:25:57]Test starting |
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.
According to the description of the pthread_cond_destroy function in glibc 2.32, it is advised to ensure that all threads blocked on the condition variable have been successfully awakened before calling this function, otherwise unpredictable situations may occur.
In the glibc 2.32 version, this testcase will hang. Therefore, it is necessary to ensure that all threads have been successfully awakened before calling pthread_cond_destroy to destroy the condition variable.
[ type description here; PLEASE REMOVE THIS LINE AND THE LINES BELOW BEFORE SUBMITTING THIS PULL REQUEST ]