Skip to content

[launch_testing] remove deprecated ready_fn feature - #589

Merged
wjwwood merged 5 commits into
masterfrom
remove_ready_fn
Apr 12, 2022
Merged

wjwwood merged 5 commits into
masterfrom
remove_ready_fn

Conversation

@wjwwood

@wjwwood wjwwood commented Feb 1, 2022

Copy link
Copy Markdown
Member

This feature was deprecated in #346 (foxy) and should be removed by now, so we'll do it in Humble.

We realized this due to this pr (thanks for that btw): #580

I'm opening in draft because I quickly did this in the browser and I'm not sure if the related ReadyAggregator class needs to be removed. So I'll let CI run first.

CI is good, but I'm still not sure about the ReadyAggregator class, looking for input on that.

Signed-off-by: William Woodall <william@osrfoundation.org>
Signed-off-by: William Woodall <william@osrfoundation.org>
Signed-off-by: William Woodall <william@osrfoundation.org>
@wjwwood wjwwood self-assigned this Feb 1, 2022
@wjwwood

wjwwood commented Feb 1, 2022

Copy link
Copy Markdown
Member Author

Preliminary CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

@wjwwood
wjwwood marked this pull request as ready for review February 2, 2022 21:11
@wjwwood
wjwwood requested a review from hidmic February 2, 2022 21:12
@adityapande-1995

Copy link
Copy Markdown
Contributor

Should this line be removed as well ?

ready_fn=lambda: self._processes_launched.set()

@wjwwood

wjwwood commented Feb 2, 2022

Copy link
Copy Markdown
Member Author

The short answer is: "I don't know"

I looked at that line, but I couldn't figure out if it is part of the test runner machinery that is unfortunately named the same as the old feature users would use, or not. That's why I ran CI, I figured that if it was the old feature I'm removing some tests should fail, but maybe that's not the case.

I also sort of traced the logic and I believe that it is still used, but the difference is that the ready_fn is passed to the wrapper and not the launch_description_fn, as it used to be.

Maybe someone more familiar with launch_testing like @ivanpauno or @hidmic could comment on it.

@hidmic

hidmic commented Feb 4, 2022

Copy link
Copy Markdown

Should this line be removed as well ?

@adityapande-1995 @wjwwood It shouldn't. That's the actual callable that the ReadyToTest action eventually invokes.

I looked at that line, but I couldn't figure out if it is part of the test runner machinery that is unfortunately named the same as the old feature users would use, or not.

TBH this whole thing is messy.

@hidmic hidmic left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@wjwwood LGTM but

if argname == 'ready_fn':
continue

should be removed too.

Signed-off-by: William Woodall <william@osrfoundation.org>
@wjwwood

wjwwood commented Feb 15, 2022

Copy link
Copy Markdown
Member Author

CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

@hidmic

hidmic commented Feb 25, 2022

Copy link
Copy Markdown

@wjwwood linters were still failing in that last CI.

Signed-off-by: William Woodall <william@osrfoundation.org>
@wjwwood

wjwwood commented Apr 7, 2022

Copy link
Copy Markdown
Member Author

New CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

@ivanpauno ivanpauno left a comment

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.

LGTM!

@audrow audrow left a comment

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.

Looks good to me!

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.

6 participants