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

Fix test rosbag2_py test compatibility with Python < 3.8 #987

Merged
merged 1 commit into from
Apr 13, 2022

Conversation

cottsay
Copy link
Member

@cottsay cottsay commented Apr 13, 2022

RHEL is currently using a Python version older than 3.8, which is when the missing_ok argument was added to Path.unlink. For better compatibility, we can just catch and ignore the FileNotFoundError.

This should resolve the persistent test failure we're seeing on RHEL.

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

RHEL is currently using a Python version older than 3.8, which is when
the `missing_ok` argument was added to Path.unlink. For better
compatibility, we can just catch and ignore the FileNotFoundError.

Signed-off-by: Scott K Logan <logans@cottsay.net>
@cottsay cottsay requested a review from a team as a code owner April 13, 2022 19:35
@cottsay cottsay requested review from gbiggs and hidmic and removed request for a team April 13, 2022 19:35
@cottsay cottsay self-assigned this Apr 13, 2022
@cottsay cottsay added the bug Something isn't working label Apr 13, 2022
Copy link
Contributor

@clalancette clalancette 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 to me with green CI.

@cottsay cottsay merged commit d5783f0 into master Apr 13, 2022
@delete-merged-branch delete-merged-branch bot deleted the cottsay/py36 branch April 13, 2022 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants