Replies: 2 comments 1 reply
-
|
Thanks for opening this! I've definitely run into test failures when I had a ruff.toml file in my /tmp directory, so I can relate. I guess most of us just don't have global ruff configs because I don't think we normally run tests in containers (I know I don't at least). Something like: env -u RUFF_OUTPUT_FORMAT cargo test ...seems to work well enough for the output format, but I haven't been able to find a nice I'm only seeing 5 failures from a (small) global ruff config file: Is that what you're seeing too? We might be able just to fix these tests, especially since they all seem related. I'm not seeing the EXE test failures locally or in CI, so that might be related to your environment too. |
Beta Was this translation helpful? Give feedback.
-
|
Apart from the EXE test failures:
affect these tests: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
when running the test suite using
cargo test, i noticed that my personal configuration from$RUFF_OUTPUT_FORMATand~/.config/ruff/pyproject.tomlleaked and effected the tests (i.e. some snapshots were different)is it intended? i can assume that the 'official' way to run tests is in docker containers, but than
i'm not a ruff programmer so i don't know if there is a way to isolate the test suite from those effects, but i assume there might be.
just something to improve the experience of new contributors.
also , i got :
on the main branch, and i'm not sure why. is it something in the cloning? or is it failing on main for everyone?
Beta Was this translation helpful? Give feedback.
All reactions