Multiple Errors while execution of Tests
See original GitHub issueEnvironment
- pip version: 19.3.1
- Python version: 3.7.3
- OS: Fedora 29
Description Tried Executing very first command $tox -e py36
Expected behavior A Good success message
How to Reproduce Maybe some environment issue, or some command is missing.
- Installed Tox
- Then Installed Python3.8
- Then Executed
$tox -e py3.7 >> error.txt
Output
Attached Output File
[error.txt](https://github.com/pypa/pip/files/4035602/error.txt)
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
How to View Multiple JUnit Assertion Errors in One Test ...
Learn an easy solution to view all of the JUnit Assertion errors in one test execution from the test automation professionals at tapQA!...
Read more >Error Messages During Test Execution - LambdaTest
Here is a list of various error messages that may happen during test execution.
Read more >JUnit tests succeed individually, but when executed together ...
These test all succeed if they are executed individually i.e. commenting out the two other tests and only executing one. However, if I...
Read more >Software Testing Errors to look out for (with examples)
In this article, we discuss some common software testing errors that a tester should be aware of. These errors are explained with examples ......
Read more >Compilation Error in Test A When Executing Test B
PROBLEM. My project contains two or more tests that contain coded steps. I receive a compilation error for Test A when I try...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hmm, I just checked this on a fresh Fedora 29 Docker image:
So it seems the stdlib is doing the correct thing by default, and the
NotADirectory
exception you get is indeed an environment problem. I don’t know what it is though. 😦The two errors are the same, something like
I believe they are tracked in #7545.