Windows CI failing
See original GitHub issueFailure seems to be coming from pytorch.
File "C:\tools\miniconda3\lib\site-packages\torch\__init__.py", line 138, in <module>
raise err
OSError: [WinError 126] The specified module could not be found. Error loading "C:\tools\miniconda3\lib\site-packages\torch\lib\caffe2_detectron_ops_gpu.dll" or one of its dependencies
cc @peterjc123 @nbcsm @guyang3532 @maxluk @gunandrose4u @mszhanyi @seemethere
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:10 (5 by maintainers)
Top Results From Across the Web
CI: Windows builds fail on `windows-latest` (aka ... - GitHub
Integration tests that run on windows don't work on windows-latest (which as of recently resolves to windows-2022 ). They do work on windows- ......
Read more >start up problem. cannot repair. ci.dll - Microsoft Community
a. Insert the Windows installation DVD into the DVD-ROM; Click Exit if the auto-menu pops up. b. Open an elevated command prompt.
Read more >Failed to do git clone from a CI CD job into a Windows Gitlab ...
Hi All, I am unable to do git clone successfully in a Gitlab runner running on Windows, while I am able to do...
Read more >GitHub Workflow CI Setup conda environment with ...
GitHub Workflow CI Setup conda environment with mambaforge failing on windows: Original error was: No module named 'numpy.core.
Read more >NPM CI task is failing intermittently from the build pipeline with ...
Developer Community. Your open channel to Microsoft engineering teams. Select a page .
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
Theoretically, (Major.Minor.Update) update change shouldn’t change the interface.
There isn’t new 11.1.x after 11.2