You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two types of failures when running the python based tests on Windows:
End-to-end execution tests are failing due to the signal.SIGALRM (used for timeout handling in the following piece of testing code) is not available for Windows
Python API unit tests using LLVM's lit testing framework are failing due to pwd module not being available in Windows. This failure is a bit puzzling as it seems to be triggered from fx.export_and_import as seen in the logs, but running the file from CLI directly such as python test\python\fx_importer\v2.3\types_test.py doesn't produce any error.
The text was updated successfully, but these errors were encountered:
1. Adds a workflow to trigger windows build in the CI similar to the
existing one for Linux to address the build CI request captured in
#3985
2. Only non-python based LIT unit tests are enabled in the workflow due
to failures reported in #4040
3. The CI is only run against `torch-nightly` since python based tests
are disabled. My understanding is that without the python based tests
there's no need to run against the `stable` version too. If that's not
the case, will enable `stable` as well. Tested that both `nightly` and
`stable` versions work fine:
https://github.com/sahas3/torch-mlir/actions/runs/13477124004
There are two types of failures when running the python based tests on Windows:
End-to-end execution tests are failing due to the
signal.SIGALRM
(used for timeout handling in the following piece of testing code) is not available for Windowstorch-mlir/projects/pt1/python/torch_mlir_e2e_test/framework.py
Lines 310 to 323 in a265d28
One possible solution is to use the https://pypi.org/project/pytest-timeout/ plugin with pytest which offers portability across different platforms.
Python API unit tests using LLVM's
lit
testing framework are failing due topwd
module not being available in Windows. This failure is a bit puzzling as it seems to be triggered fromfx.export_and_import
as seen in the logs, but running the file from CLI directly such aspython test\python\fx_importer\v2.3\types_test.py
doesn't produce any error.The text was updated successfully, but these errors were encountered: