Add gemm tuning configs for weekly tuning CI #662
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds our tuning configs to be used for the weekly tuning, the confluence page contains more details about the CI pipelines.
The fallback tuned configs are required for now for the nighlty regression CI because the navi4x machine was not stable enough to run a full tuning consistently. They changed the hardware and firmware to a newer revision so I will test it again. If it is stable we can remove the fallback in a separate PR.
I also removed the old regression script because the nightly regression CI uses the triton-reporting-system from the kernel team instead of the pytest script.