-
Notifications
You must be signed in to change notification settings - Fork 795
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
[17148] Improve behavior when HAVE_STRICT_REALTIME is not set. #3288
Conversation
Signed-off-by: Miguel Company <[email protected]>
Signed-off-by: Miguel Company <[email protected]>
Signed-off-by: Miguel Company <[email protected]>
Signed-off-by: Miguel Company <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good so far but I think there are some other instances of try_lock_until that are not accounted for in DataReaderImpl
and SubscriberHistory
.
Our implementation of shared_mutex
could also be modified to be in line with the new TimedMutex
implementation since it also has timed locking capabilities.
Signed-off-by: Miguel Company <[email protected]>
fa2f529
to
4d07531
Compare
Changes for
I had a look at it, but we are not using |
@richiprosima Please test this |
@richiprosima Please test mac again to check whether the failed test is flakey |
https://github.com/Mergifyio backport 2.9.x 2.8.x 2.6.x 2.1.x |
* Refs #17148. Avoid try_lock_until on RTPSParticipantImpl. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on RTPSReader. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on ResourceEvent. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Using right clock on custom TimedMutex. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on DataReaderImpl. Signed-off-by: Miguel Company <[email protected]> --------- Signed-off-by: Miguel Company <[email protected]> (cherry picked from commit 0cf43de)
* Refs #17148. Avoid try_lock_until on RTPSParticipantImpl. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on RTPSReader. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on ResourceEvent. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Using right clock on custom TimedMutex. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on DataReaderImpl. Signed-off-by: Miguel Company <[email protected]> --------- Signed-off-by: Miguel Company <[email protected]> (cherry picked from commit 0cf43de)
* Refs #17148. Avoid try_lock_until on RTPSParticipantImpl. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on RTPSReader. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on ResourceEvent. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Using right clock on custom TimedMutex. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on DataReaderImpl. Signed-off-by: Miguel Company <[email protected]> --------- Signed-off-by: Miguel Company <[email protected]> (cherry picked from commit 0cf43de)
* Refs #17148. Avoid try_lock_until on RTPSParticipantImpl. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on RTPSReader. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on ResourceEvent. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Using right clock on custom TimedMutex. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on DataReaderImpl. Signed-off-by: Miguel Company <[email protected]> --------- Signed-off-by: Miguel Company <[email protected]> (cherry picked from commit 0cf43de) # Conflicts: # src/cpp/fastdds/subscriber/DataReaderImpl.cpp
✅ Backports have been created
|
#3292) * Improve behavior when HAVE_STRICT_REALTIME is not set (#3288) * Refs #17148. Avoid try_lock_until on RTPSParticipantImpl. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on RTPSReader. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on ResourceEvent. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Using right clock on custom TimedMutex. Signed-off-by: Miguel Company <[email protected]> * Refs #17148. Avoid try_lock_until on DataReaderImpl. Signed-off-by: Miguel Company <[email protected]> --------- Signed-off-by: Miguel Company <[email protected]> (cherry picked from commit 0cf43de) # Conflicts: # src/cpp/fastdds/subscriber/DataReaderImpl.cpp * Fix conflicts. Signed-off-by: Miguel Company <[email protected]> * Add implementation to SubscriberHistory. Signed-off-by: Miguel Company <[email protected]> * Fixed unused variable warnings Signed-off-by: Javier Santiago <[email protected]> --------- Signed-off-by: Miguel Company <[email protected]> Signed-off-by: Javier Santiago <[email protected]> Co-authored-by: Miguel Company <[email protected]> Co-authored-by: Javier Santiago <[email protected]>
Description
This PR avoids using
try_lock_until
whenHAVE_STRICT_REALTIME
has not been set (in which case it was using a 24 hours timeout).It also fixes a bug in the custom TimedMutex, which was always using
steady_clock::now
for calculating the required timeout.@Mergifyio backport 2.9.x 2.8.x 2.6.x 2.1.x
Contributor Checklist
versions.md
file (if applicable).Reviewer Checklist