-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
range_test and sge_test not picked up by tox due to being executable #2757
Comments
@lallea FYI |
Nice catch!! |
Thank you @Tarrasch! By the way, isn't this error kind of problematic, that tox just silently ignores executable files? How would we prevent it from happening again? I can definitely see someone accidentally modifying file permissions again, tests go through and no one notices anything. |
It is worrying yes. Not sure If I know a general solution to this though. (that's also practical :)) |
While developing some new functionality in
luigi.tools.range
I ran therange_test.py
file manually and noticed that it had multiple failing tests that were unrelated to my changes, even on a clean master with no changes at all. Strangely, tox goes through and the build passes anyway. This happens because the whole file is ignored. The reason the file is ignored is because it is set as executable (755) which apparently causes tox to ignore it.Steps to reproduce
tox
range_test.py
file and it has multiple issues, FAILED (failures=2, errors=6):cd test && python -m unittest range_test
chmod 644 range_test.py
The only executable files I could find were
range_test.py
andcontrib/sge_test.py
.Solution
We need to chmod the concerned files to match the others (644) and fix the failing tests. If we can't fix them right now we need to temporarily ignore the individual tests and create new Github issues. I am in progress of doing this but wanted to report the error in case anyone else encounters the problem.
The text was updated successfully, but these errors were encountered: