-
-
Notifications
You must be signed in to change notification settings - Fork 663
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
Not all tests are run in Azure's Python builds #270
Comments
Confirming with PR #272 that this is a problem: Only 42 tests instead of 81. |
Is your local build more recent than 9d47bda? |
On my computer (Linux build), for the following commit:
I get:
|
FYI: I was just thinking that I should check the dashboards and the Python nighly builds to see if all the Python tests where running on there. But something might be broken there as only the Mac build is done, but fails. The linux and Windows builds do not seem to return any result (at least for yesterday, 12/06/18). I thought I would report this issue here as it may be related to the original problem I reported. |
I confirmed that I could reproduce the 81 tests with a local build. The macOS Nightly Python build is also only reporting 45 tests. We'll eventually bring the Linux and Windows build back online. I suspect there is a CMake variable caching or scope issue that is revealed by running configuration through the CTest script... |
Update: I was able to reproduce locally running via CTest script. With setting |
Thanks for solving that mystery. The failing tests might be related to #271, but you can double check that it addresses all the issues listed on the dashboard. |
Description
Not all Python tests are run on Azure's Python Build (42 instead of 81).
Steps to Reproduce
To check what Python tests are run in Azure's Python's builds, one can connect to dev.azure.com from the check result links on Github. If the PR has been closed, one can still access the check result links by clicking on the green check mark or red cross to expand the list of checks. For example, for PR #268 , the results of the Linux Python Builds are available here.
On the
Build and test
line, one can click on the blue icondownload the log
to download a zip file containing the build and test log.After that, the following command can be run to count the number of Python tests that were run:
more 7.txt|grep Python |grep Test |grep '#' |wc -l
Expected behavior
In theory, there should be around 80 tests run for Python builds, based on what happens on my machine.
Actual behavior
Only 42 Python tests are run.
Reproducibility
Unknown as the PR used to reproduce this step was the first re-activating about 40 tests that had been accidently deactivated.
Versions
At least for PR #268
Environment
I haven't checked the logs on Max and Windows, but I expect the same behavior since all the tests were reporting as passing even though there should have been some tests failing. This demonstrates that the tests that should have failed were not run.
The text was updated successfully, but these errors were encountered: