[CI] Hotfix test_gemm_autotune update

[VeeraRajasekhar]

Description

Please include a brief summary of the changes, relevant motivation and context.

Fixes # (issue)

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Infra/Build change
• Code refactoring

Changes

Please list the changes introduced in this PR:

• Change A
• Change B

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[ipanfilo]

The fix is understood bu can you clarify how the problem manifest itself. And it seems escaped GEMM autotune test so the latter may need improve

[VeeraRajasekhar]

The fix is understood bu can you clarify how the problem manifest itself. And it seems escaped GEMM autotune test so the latter may need improve

While I was working on the adding gelu aux, I tested locally with the correct order, while pushing I had a code cleanup then the line was misplaced.