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
Fix: Show actual error messages in Triton installation script (#49)
Summary:
## Problem
When Triton import failed in CI scripts, errors were silently discarded (`2>/dev/null`) making debugging impossible. Additionally, the libstdc++ version was too old to support newer Triton builds.
## Solution
- **Error Visibility**: Replace `2>/dev/null` with `2>&1` to capture and display actual error messages
- **Controlled Exit**: Use `set +e`/`set -e` around import tests to prevent immediate script termination
- **libstdc++ Upgrade**: Update from 12.3.0 to 15.1.0 for `GLIBCXX_3.4.32` support
- **Enhanced Diagnostics**: Add Python environment info when imports fail
## Changes
- `.ci/install-triton.sh` - Source installation script with improved error handling + libstdc++ upgrade
- `.ci/install-triton-pip.sh` - Pip installation script with same error handling improvements
Pull Request resolved: #49
Reviewed By: davidberard98
Differential Revision: D79449990
Pulled By: FindHao
fbshipit-source-id: 32ff5c2c8832fcdaef965ef226e59a514ee2a3c3
0 commit comments