Skip to content

Unpin mypy.#617

Merged
clalancette merged 2 commits intomasterfrom
clalancette/unpin-mypy
Feb 16, 2022
Merged

Unpin mypy.#617
clalancette merged 2 commits intomasterfrom
clalancette/unpin-mypy

Conversation

@clalancette
Copy link
Copy Markdown
Contributor

Signed-off-by: Chris Lalancette clalancette@openrobotics.org

This should fix the warnings we are seeing on Jammy, like https://ci.ros2.org/job/ci_linux/16057/ . On the other hand, I don't know what the situation is going to be like on Foxy and Galactic on Focal, so testing still needs to be done here.

@clalancette
Copy link
Copy Markdown
Contributor Author

clalancette commented Feb 7, 2022

CI using this branch.

Rolling:

  • Focal Linux Build Status
  • Focal Linux-aarch64 Build Status
  • Windows Build Status
  • Jammy Linux Build Status
  • Jammy Linux-aarch64 Build Status

Foxy:

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

(if everything above is happy, I'll run Galactic CI tomorrow)

@clalancette
Copy link
Copy Markdown
Contributor Author

OK, so as suspected this fixed things on Jammy, but broken things for Foxy.

That leaves us with a few options:

  1. Continue to use pip to install mypy (we have to for Windows), but conditionalize the version depending on Focal or Jammy.
  2. Install mypy from distribution packages on Focal and Jammy, and only install from pip for Windows.
  3. Disable the mypy tests for sros2 on Foxy (it's the only thing that is failing).

@nuclearsandwich Opinions?

@nuclearsandwich
Copy link
Copy Markdown
Member

Install mypy from distribution packages on Focal and Jammy, and only install from pip for Windows.

If I recall correctly pinning to the version in Focal was the agreed upon solution in the 2021-06-15 ROS 2 meeting but there's no mention there of doing so via system package or pip. I'm in favor of using the debs and rpms in CI in order to more closely replicate the buildfarm environment.

@clalancette
Copy link
Copy Markdown
Contributor Author

If I recall correctly pinning to the version in Focal was the agreed upon solution in the 2021-06-15 ROS 2 meeting but there's no mention there of doing so via system package or pip. I'm in favor of using the debs and rpms in CI in order to more closely replicate the buildfarm environment.

Yep, agreed. That is my preferred solution as well. I'll try this out and see how it goes.

@clalancette
Copy link
Copy Markdown
Contributor Author

clalancette commented Feb 8, 2022

All right, the new code I pushed is more complicated, but also should get us closer to what we want. Let's see how this goes:

Rolling:

  • Focal Linux Build Status
  • Focal Linux-aarch64 Build Status
  • Windows Build Status
  • Jammy Linux Build Status

Foxy:

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

(if this goes well, I'll run additional jobs for Galactic and RHEL tomorrow)

Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
@clalancette clalancette force-pushed the clalancette/unpin-mypy branch from 25718bf to 668c819 Compare February 15, 2022 21:40
@clalancette
Copy link
Copy Markdown
Contributor Author

clalancette commented Feb 15, 2022

I've redone this completely, and what I've done should make it much more robust. Let's try another CI to see what happens:

Rolling:

  • Ubuntu Focal Build Status
  • Ubuntu Focal-aarch64 Build Status
  • Windows Build Status
  • Ubuntu Jammy Build Status

Foxy:

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

Copy link
Copy Markdown
Member

@nuclearsandwich nuclearsandwich left a comment

Choose a reason for hiding this comment

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

Looks good so far. Hanging on to the ✔️ until CI comes back happy.

Co-authored-by: Steven! Ragnarök <nuclearsandwich@users.noreply.github.com>
@clalancette clalancette marked this pull request as ready for review February 16, 2022 13:03
@clalancette
Copy link
Copy Markdown
Contributor Author

CI was really happy with this, so I converted it to a real PR. Please take another look when you get a chance.

@clalancette
Copy link
Copy Markdown
Contributor Author

clalancette commented Feb 16, 2022

Here's CI just up to ament_cmake, to test that the latest variable names don't have a typo. If this is successful, I'm going to go ahead and merge.

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

@clalancette clalancette merged commit 2453630 into master Feb 16, 2022
@delete-merged-branch delete-merged-branch bot deleted the clalancette/unpin-mypy branch February 16, 2022 20: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