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

execute_test.py pollutes test output with error traces (MacOS) #1713

Open
jotaen4tinypilot opened this issue Dec 20, 2023 · 0 comments
Open
Labels
bug Something isn't working

Comments

@jotaen4tinypilot
Copy link
Contributor

jotaen4tinypilot commented Dec 20, 2023

Follow-up issue of #1642.

We were able to silence the undesired stacktrace printing via #1708 – this, however, only appears to work on Linux systems and not on MacOS, because on MacOS, the multiprocessing package behaves differently.

We weren’t able to find a suitable workaround for MacOS, except if we’d account for this issue inside the underlying execute.py module (e.g. by trying to silence stderr there, with a /dev/null redirect). That is probably not a good trade-off, because we’d potentially be risking to change production behaviour only to fix a minor, local testing issue. There might be other approaches to solve this problem, though.

@jotaen4tinypilot jotaen4tinypilot added the bug Something isn't working label Dec 20, 2023
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

No branches or pull requests

1 participant