-
Notifications
You must be signed in to change notification settings - Fork 50
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
2021.7.6: pytest is failing #416
Comments
Original comment by Matthew Barnett (Bitbucket: mrabarnett, GitHub: mrabarnett). So, you’re using pytest, but giving it an argument it doesn’t understand? I haven’t used pytest. I use unittest because that’s what the re module uses:
|
Original comment by Tomasz Kłoczko (Bitbucket: [Tomasz Kłoczko](https://bitbucket.org/Tomasz Kłoczko), ). On first look it looks like pytest argument is passed to Temporary I’ve added that failing unit in my rpm spec fiels to list of deselected units so no ruch :slight_smile: BTW you should not use “python -m unittest” beause module executed that way adds upfront to sys.path current directory and $PYTHONPATH will be used only if in curret directory will be no module. Result will be that it will be tested not what has been installed in </install/prefix> but source tree. |
Original comment by Matthew Barnett (Bitbucket: mrabarnett, GitHub: mrabarnett).
|
Original comment by Tomasz Kłoczko (Bitbucket: [Tomasz Kłoczko](https://bitbucket.org/Tomasz Kłoczko), ). “Command-Line Interface”? .. hmm .. what you mean? Just tested 2021.10.23 and issu estill is around. Thre are some new warnings
|
Original comment by Matthew Barnett (Bitbucket: mrabarnett, GitHub: mrabarnett). I’m talking about the Python docs on unittest, and the section titled “Command-Line Interface”. |
See #448 (comment) |
Original report by Tomasz Kłoczko (Bitbucket: [Tomasz Kłoczko](https://bitbucket.org/Tomasz Kłoczko), ).
Just normal build, install and test cycle used on building package from non-root account:
The text was updated successfully, but these errors were encountered: