The integration tests CI workflow typically takes around 40-50 minutes, with an occasional 60 minute run. This is slow and could be improved by caching the compiled Triton objects.
The "Install Triton" step is the one consuming most all of that time. There seem to have been some efforts to improve this in the past: ccache is set up and shows ~700 files in the cache but half of those cache miss (link). We can see, however, that the entire Triton project rebuilds each time — all 510 files (link). This indicates that something is not configured correctly, likely between CMake, ccache, and our workflow. If any number of those compiled objects could be cached, that would be saved time.
The integration tests CI workflow typically takes around 40-50 minutes, with an occasional 60 minute run. This is slow and could be improved by caching the compiled Triton objects.
The "Install Triton" step is the one consuming most all of that time. There seem to have been some efforts to improve this in the past: ccache is set up and shows ~700 files in the cache but half of those cache miss (link). We can see, however, that the entire Triton project rebuilds each time — all 510 files (link). This indicates that something is not configured correctly, likely between CMake, ccache, and our workflow. If any number of those compiled objects could be cached, that would be saved time.