-
Notifications
You must be signed in to change notification settings - Fork 49
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
Workflow to test Triton with nightly PyTorch wheels on Windows #3204
Conversation
- name: Run core tests | ||
run: | | ||
Invoke-BatchFile "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64 | ||
${{ env.NEW_WORKSPACE }}\venv\Scripts\activate.ps1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Judging by the logs, the tests are run with the python that is installed on the system (instead of the virtual environment). Perhaps we need to activate the environment inside of scripts/test-triton.sh
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, working on it. In worst case, I will rewrite (parts of) test-triton.sh
in Python.
Invoke-BatchFile "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64 | ||
${{ env.TRITON_TEST_CMD }} --core | ||
|
||
- name: Run interpreter tests | ||
run: | | ||
Invoke-BatchFile "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64 | ||
${{ env.TRITON_TEST_CMD }} --interpreter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cd ${{ env.NEW_WORKSPACE }}
?
Invoke-BatchFile "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64 | |
${{ env.TRITON_TEST_CMD }} --core | |
- name: Run interpreter tests | |
run: | | |
Invoke-BatchFile "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64 | |
${{ env.TRITON_TEST_CMD }} --interpreter | |
Invoke-BatchFile "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64 | |
cd ${{ env.NEW_WORKSPACE }} | |
${{ env.TRITON_TEST_CMD }} --core | |
- name: Run interpreter tests | |
run: | | |
Invoke-BatchFile "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64 | |
cd ${{ env.NEW_WORKSPACE }} | |
${{ env.TRITON_TEST_CMD }} --interpreter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As you build triton in new workspace:
- name: Setup Triton
run: |
Invoke-BatchFile "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64
.venv\Scripts\activate.ps1
cd ${{ env.NEW_WORKSPACE }}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "new workspace" is required only to build Triton (since cl.exe does not support long names). Everything else works from the standard workspace.
run: | | ||
Invoke-BatchFile "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64 | ||
${{ env.NEW_WORKSPACE }}\venv\Scripts\activate.ps1 | ||
pip install defusedxml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pip install defusedxml | |
cd ${{ env.NEW_WORKSPACE }} | |
pip install defusedxml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not needed, the standard workspace works.
On Windows, this points to Python that is not from venv.
Fixes #3177.