Skip to content
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

👨‍🌾 Revert "make type support helper supported for service (#2209)" #2392

Closed
wants to merge 1 commit into from

Conversation

Blast545
Copy link
Contributor

@Blast545 Blast545 commented Dec 15, 2023

This reverts commit d9b2744.

The PR I'm proposing to revert seems to be breaking the cppcheck, causing a timeout in nightly_win_deb.

I'm opening this PR in draft to test with CI if this was actually the cause of the problem.

Reference failure we'll try to replicate: https://ci.ros2.org/view/nightly/job/nightly_win_deb/2942/

CI test, CI_Windows, debug, packages-up-to rclcpp_lifecycle
Build Status

This reverts commit d9b2744.

Signed-off-by: Jorge Perez <jorge.perez@swift-nav.com>
@clalancette
Copy link
Contributor

Do we still need this PR? It looks like the nightly_win_deb is generally passing without it: https://ci.ros2.org/view/nightly/job/nightly_win_deb/

That said, if we run into further problems here, my first thought would be to increase the cppcheck timeout. We've done that elsewhere.

@Blast545
Copy link
Contributor Author

I was exactly right now looking into the results of the PR. I never had any intention to merge this one, just wanted to check if the last PR to the repo had any influence in the appearance ratio of the issue.

Given the recent history of the job, it seems the problem has stopped appearing while it happened consecutively 4 times last week. After a manual check, I realized it has happened as well in the past. I'm starting to think that the capabilities of the agent might be the actual cause behind the yellows last week.

Do you think increasing the timeout from 300s to something like 350s would be OK? It's a lot of time for just one linter.

@clalancette
Copy link
Contributor

Do you think increasing the timeout from 300s to something like 350s would be OK? It's a lot of time for just one linter.

Yeah, I think that is OK for now (though I might suggest 360 seconds, just so it is an even number of minutes).

I agree it is a long time, but Windows is the only platform where cppcheck still works. Eventually maybe we should just disable it, but that is a larger discussion.

@Blast545
Copy link
Contributor Author

Roger that, will open a PR to increase that timeout and close this PR.

@Blast545 Blast545 closed this Dec 20, 2023
@Blast545 Blast545 deleted the blast545/revert_rclcpp_209 branch April 15, 2024 16:18
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.

2 participants