frozenleaves/pytorch
1
0
Fork 0
mirror of https://github.com/pytorch/pytorch.git synced 2025-10-20 21:14:14 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated Debugging using with ssh for Github Actions (markdown)

Vincent Moens
2024-07-10 11:44:27 +01:00
parent 930c1ac989
commit 9fc63d31df
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Debugging-using-with-ssh-for-Github-Actions.md

@ -41,7 +41,7 @@ VSCode's remote SSH extension works with both Linux and Windows CI machines. Add
```
## Linux
Once you are connected through ssh, you may need to enter a docker container. Run `docker ps` to check if there are any docker containers running. Note that your CI job might be in the process of initiating a docker container, which means it will not show up yet. It is best to wait until the CI job reaches a step where it is building pytorch or running pytorch tests. If the job does have a docker container, run `docker exec -it CONTAINER_ID /bin/bash` to connect to it.
Once you are connected through ssh, you may need to enter a docker container. Run `docker ps` to check if there are any docker containers running. Note that your CI job might be in the process of initiating a docker container, which means it will not show up yet. It is best to wait until the CI job reaches a step where it is building pytorch or running pytorch tests. If the job does have a docker container, run `docker exec -it CONTAINER_ID /bin/bash` to connect to it (or simply run `docker exec -it $(docker ps | awk 'NR==2 {print $1}') /bin/bash` directly to parse the CONTAINER_ID).
Now you can find the pytorch working directory, which could be ~/workspace or ~/project, and run commands locally to debug the failure.