CI fails on windows: ci/circleci: unittest_windows_cpu_pyX.Y
See original GitHub issueTests on windows are started failing:
- https://app.circleci.com/pipelines/github/pytorch/vision/18503/workflows/3c477207-67b9-45c8-8960-ab3efb40b8b1/jobs/1497031
- https://app.circleci.com/pipelines/github/pytorch/vision/18503/workflows/3c477207-67b9-45c8-8960-ab3efb40b8b1/jobs/1496973
test/test_models.py::test_classification_model[cpu-regnet_y_16gf] PASSED [ 79%]
test/test_models.py::test_classification_model[cpu-regnet_y_32gf] PASSED [ 79%]
test/test_models.py::test_classification_model[cpu-regnet_y_128gf]
Exited with code exit status 127
CircleCI received exit code 127
It started appearing on PyTorch core nightly 20220622
Issue Analytics
- State:
- Created a year ago
- Comments:18 (13 by maintainers)
Top Results From Across the Web
Test Summary Troubleshooting - CircleCI Support
The test summary in the UI is a place where we display some basic information about tests such as which tests failed, or...
Read more >Windows store_test_results failing tests don't fail the build
I recently added windows build and test jobs to our existing CI using the win/default executor and powershell. After running the testsuite ...
Read more >Unit test fails due to carriage return - CircleCI Discuss
I have a problem dealing with circle ci running test when deploying. I have unit test that has a formatted message.
Read more >Testing works fine when run locally but fails on Circleci
In my experience, errors of this kind are down to a differing environment between your local tests and your CI tests.
Read more >Building and testing an ASP.NET Core application - CircleCI
This article explores the use of CircleCI's Windows execution environment to build and run tests for a simple calculator application built ...
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 Free
Top 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
@vfdev-5 the failure is suspicious because it’s on a very large model. Can you try skipping the specific test to see if this is related to issues on CircleCI side rather than on core? Another thing we can do to confirm that the core is not the issue, is to fix the nightly the the one before and rerun the job. If it fails we will know it’s the CircleCI.
For my macbook it does not fail, but I think this is expected (in the circle ci, only windows one failing and probably because of resource problem like memory)