Skip to content

<2.2.x> Explicitly set reliability [10777] #1810

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

Merged
merged 1 commit into from
Apr 23, 2021

Conversation

JLBuenoLopez
Copy link
Contributor

Backport #1794 to <2.2.x>

* Explicitly set reliability

Signed-off-by: EduPonz <[email protected]>

* Remove unnecessary log in cmake

Signed-off-by: EduPonz <[email protected]>

* Set reliability option with -R

Signed-off-by: EduPonz <[email protected]>
Signed-off-by: JLBuenoLopez-eProsima <[email protected]>
@JLBuenoLopez JLBuenoLopez changed the title <2.2.x> Explicitly set reliability <2.2.x> Explicitly set reliability [10777] Mar 8, 2021
@JLBuenoLopez
Copy link
Contributor Author

CI failures are unrelated and caused by already known flaky tests. The only exception is the building error in discovery_server. This is solved in #1811 which backports the SUPER CLIENT feature to <2.2.x>

Copy link
Member

@MiguelCompany MiguelCompany left a comment

Choose a reason for hiding this comment

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

LGTM

@MiguelCompany MiguelCompany merged commit 1e30b4d into 2.2.x Apr 23, 2021
@MiguelCompany MiguelCompany deleted the feature/performance/2.2.X-explicit_reliability branch April 23, 2021 07:51
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.

3 participants