-
Notifications
You must be signed in to change notification settings - Fork 84
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
reproducer tests: grab output/error, and use the correct python #1554
base: main
Are you sure you want to change the base?
Conversation
Note this bit from the docs:
https://docs.python.org/3.13/library/subprocess.html#module-subprocess |
The errors from the broken CI were:
These are similar to issues I hit on my local system: the environment from a Instead of But really want to hear from @kiya00 first. |
@mruberry pointed me at https://stackoverflow.com/questions/29523246/python-subprocess-is-running-a-different-version-of-python which had great advice---this was indeed the problem. I've updated the patch to use |
CI failure looks relevant:
|
agh, thanks though. will push a fix in a sec |
Had a minor issue on my system and needed the actual output to debug what was going wrong.
This ensures the python we pass to subprocess.run is the same one as the thing that's running.
9797ac0
to
77ff13b
Compare
for more information, see https://pre-commit.ci
Most recent CI issue was |
Had a minor issue on my system and needed the output to debug what was going wrong.
What does this PR do?
This changes what assertion errors will print out in the case of an error. Specifically this gives the output from
subprocess.run
in some tests.PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.