Skip to content

Conversation

whitslack
Copy link
Collaborator

@whitslack whitslack commented Aug 23, 2025

When running the integration test suite in a deeply nested directory tree, the path name of the Unix domain socket might be longer than can fit in a struct sockaddr_un. On Linux, we can use the /proc/self/cwd trick to shorten the path name.

Changelog-Fixed: Integration tests no longer fail when run in a deeply nested directory on Linux.

Checklist

Before submitting the PR, ensure the following tasks are completed. If an item is not applicable to your PR, please mark it as checked:

  • The changelog has been updated in the relevant commit(s) according to the guidelines.
  • Tests have been added or modified to reflect the changes.
  • Documentation has been reviewed and updated as needed.
  • Related issues have been listed and linked, including any that this PR closes. None found.

@whitslack whitslack force-pushed the socket-path-name-workaround branch from ec19206 to e16a719 Compare August 24, 2025 02:50
@whitslack whitslack changed the title test_misc.py: work around socket path name too long on Linux tests: work around socket path name too long on Linux Aug 24, 2025
When running the integration test suite in a deeply nested directory
tree, the path name of the Unix domain socket might be longer than can
fit in a struct sockaddr_un. On Linux, we can use the /proc/self/cwd
trick to shorten the path name.

Changelog-Fixed: Integration tests no longer fail when run in a deeply nested directory on Linux.
@whitslack whitslack force-pushed the socket-path-name-workaround branch from e16a719 to 324302d Compare August 24, 2025 03:26
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.

1 participant