Remove word boundaries to match error anywhere in the string

[dorde-antic]

Motivation

Resolve https://github.com/ROCm/rocMLIR-internal/issues/2180

Technical Details

The change is simple but effective - it will now detect any line in the tuning log that contains "error" as a substring, making our CI error detection much more comprehensive.
Before: /(?i)\berror\b/
Used word boundaries (\b) that only matched "error" as a complete word
After: /(?i)error/
Removed word boundaries to match "error" anywhere in the string
Now the tuning error detection will catch:
✅ KeyError
✅ TypeError
✅ ValueError
✅ RuntimeError
✅ SomethingError
✅ error (standalone word still works)
✅ Any other text containing "error" (case-insensitive)

Test Plan

Test Result

Submission Checklist

• Look over the contributing guidelines at https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.

[dhernandez0]

are there any "error" message in the log that doesn't mean there's an error? For example, I think cmake can produce _ERROR_... and it doesn't mean an actual error.

[umangyadav]

are there any "error" message in the log that doesn't mean there's an error? For example, I think cmake can produce _ERROR_... and it doesn't mean an actual error.

It is only seaching for "error" in tuning logs.