Skip to content

enable/disable rosout logging in each node individually#469

Merged
ivanpauno merged 3 commits intoros2:masterfrom
Barry-Xu-2018:topic-node-enable-rosout
Dec 5, 2019
Merged

enable/disable rosout logging in each node individually#469
ivanpauno merged 3 commits intoros2:masterfrom
Barry-Xu-2018:topic-node-enable-rosout

Conversation

@Barry-Xu-2018
Copy link
Copy Markdown
Contributor

@Barry-Xu-2018 Barry-Xu-2018 commented Dec 2, 2019

This is following PR for ros2/rcl#532.
Provide option to enable/disable rosout logging for rclpy.
Related issue is ros2/rcl#510.

There are 2 commits. One is for implementation. The other is for test codes.

There is a problem on test. Test codes needs python3-parameterized package.
'python3-parameterized' package is not supported currently in python test of ros2.
Whether do we can use 'python3-parameterized' this time?
If yes, do I need to update other repositories? (such as rosdistro, ros2 CI or some document) Not very clear about these steps.

@Barry-Xu-2018
Copy link
Copy Markdown
Contributor Author

@ivanpauno

Please review this PR.

@Barry-Xu-2018 Barry-Xu-2018 changed the title Node enable rosout enable/disable rosout logging in each node individually Dec 2, 2019
Signed-off-by: Barry Xu <Barry.Xu@sony.com>
@Barry-Xu-2018
Copy link
Copy Markdown
Contributor Author

@ivanpauno

I have updated test codes based on pytest.
Please review again.

@fujitatomoya
Copy link
Copy Markdown
Collaborator

@Barry-Xu-2018 @ivanpauno

LGTM

@ivanpauno
Copy link
Copy Markdown
Member

ivanpauno commented Dec 4, 2019

  • Linux Build Status
  • AArch64 Build Status
  • macOS Build Status
  • Windows Build Status

Failures are all unrelated, and being fixed by #471.

@ivanpauno
Copy link
Copy Markdown
Member

Going in! Thanks for the contribution @Barry-Xu-2018 !

@ivanpauno ivanpauno merged commit 23827e5 into ros2:master Dec 5, 2019
)

node.get_logger().info('SOMETHING')
executor.spin_once(timeout_sec=1)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@ivanpauno (tagging you because you reviewed it), watch out for things like this. It's really fragile, we're seeing this test fail a lot either due to the timeout before the event or because spinning once does not guarantee that the event you wanted handled was the one that would be handled...

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@wjwwood

our bad, sorry about that.
we will submit issue against problem and try to fix it.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks @wjwwood.
I overlooked that when reviewing, but the test is definitely flaky.

I've created an issue #546.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@fujitatomoya if you're not planning to work on a fix in a near future, let me know and I will work on it. Thanks!

Copy link
Copy Markdown
Collaborator

@fujitatomoya fujitatomoya Apr 24, 2020

Choose a reason for hiding this comment

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

@ivanpauno

i think i can work on this early next week, but if you already have idea, you can go ahead.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@wjwwood

Thank you for pointing out my mistake. I will fix it.

@ivanpauno @fujitatomoya

It's my fault. I will fix this problem tomorrow in #546.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

No worries, I wasn't trying to call anyone out, just wanted to point it out before I forgot and explain why it is fragile.

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.

5 participants