ros: remove generator warnings from linter spread tests

[cmatsuoka]

• Have you followed the guidelines for contributing?
• Have you signed the CLA?
• Have you successfully run make lint?
• Have you successfully run pytest tests/unit?

---

[cmatsuoka]

@artivis, please leave a comment if you think this is incorrect.

[artivis]

Actually not sure what's going on here (with respect to #4184). Friendly ping @Guillaumebeuzeboc .

[Guillaumebeuzeboc]

Actually not sure what's going on here (with respect to #4184). Friendly ping @Guillaumebeuzeboc .

Was the linter updated?

[cmatsuoka]

The linter was not changed AFAIK (but @mr-cal can confirm this), any recent changes in the ROS libraries?

[mr-cal]

The linter was not changed AFAIK (but @mr-cal can confirm this), any recent changes in the ROS libraries?

No changes to our linters, so a change to the ROS library or its dependencies is the likely cause.

[mr-cal]

P.S. - This is the 3rd time this has failed (1 and 2). At some point, we should consider a less hard-coded way to test this.

[codecov-commenter]

Codecov Report

Merging #4202 (ea38379) into main (530ad01) will not change coverage.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main    #4202   +/-   ##
=======================================
  Coverage   93.90%   93.90%           
=======================================
  Files         569      569           
  Lines       43746    43746           
=======================================
  Hits        41078    41078           
  Misses       2668     2668           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more