Skip to content

Going back to the old way of running e2e specs #774

Going back to the old way of running e2e specs

Going back to the old way of running e2e specs #774

Re-run triggered January 13, 2026 17:14
Status Failure
Total duration 4m 13s
Artifacts

ci.yml

on: pull_request
check_format
15s
check_format
Matrix: platform_specs
Matrix: api_without_auth
Fit to window
Zoom out
Zoom in

Annotations

1 error
api_without_auth (windows-latest)
Failed to start upterm - socket not found after maximum retries. Diagnostics: - Upterm data directory: C:\Users\RUNNER~1\AppData\Local\Temp\upterm-data - Expected socket directory: C:\Users\RUNNER~1\AppData\Local\Temp\upterm-data\runtime\upterm - Socket directory does not exist - Tmux sessions: upterm-wrapper: 1 windows (created Tue Jan 13 17:18:11 2026) - Tmux error log: - Upterm command output: - Upterm binary check: Upterm version 0.21.1 Git commit: 059c8c48d67ef06b491d82cbca45a506fdd542e2 Build date: 2026-01-08T05:35:30Z - XDG_RUNTIME_DIR (passed to upterm): /c/Users/RUNNER~1/AppData/Local/Temp/upterm-data/runtime - XDG_RUNTIME_DIR (actual directory): C:\Users\RUNNER~1\AppData\Local\Temp\upterm-data\runtime - USER: not set - UID: unknown - Platform: win32 === Troubleshooting Steps === 1. Check tmux and upterm are installed and in PATH 2. Verify upterm-server setting is correct 3. Check network connectivity to upterm server 4. Review the logs above for specific error messages 5. On Windows: Verify MSYS2 environment is working Please report this issue with the above diagnostics at: https://github.com/owenthereal/action-upterm/issues