[HOTFIX][4.5] Logging Warning->Info when PerfConfigs from db can't be deserialized or invalid (SWDEV-288975)

[JehandadKhan]

No description provided.

[atamazov]

@JehandadKhan This should be merged into staging branch, isn't it?

[atamazov]

@JehandadKhan And PR title should contain not [4.1.x] but [4.5], right?

[atamazov]

This PR only works for records that have incorrect format (e.g. incorrect number of comma-separated-numbers). But there could be records that have correct format but invalid from the Solver's point of view (solver::IsValidPerformanceConfig() returns false). I recommend borrowing also #746, which resolves the latter problem.

[atamazov]

Please go ahead if this works for you as is.

[atamazov]

@JehandadKhan Please let me know if you need more assistance; I can polish this PR for you.

[junliume]

@JehandadKhan Please let me know if you need more assistance; I can polish this PR for you.

It might be late for Central Time zone (and reaaaaly late for your time zone) while still okay for me, I am making changes according to your advice now.

Update: @atamazov if you have it already please make those changes :)

[JehandadKhan]

@JehandadKhan Please let me know if you need more assistance; I can polish this PR for you.

@atamazov Please go ahead

[atamazov]

I'll look here tomorrow SPB morning and make changes if necessary ;)

[junliume]

I'll look here tomorrow SPB morning and make changes if necessary ;)

I made some preliminary changes in order to kick off another round of CI.

[atamazov]

@JehandadKhan This should be merged into staging branch, isn't it?

@junliume @JehandadKhan If you want to merge directly to the release branch, then please cherry-pick the same also into staging -- let's keep both in sync, so we'll be able to add more commits to staging and merge into release, if need arise.

[atamazov]

LGTM!

[junliume]

@JehandadKhan This should be merged into staging branch, isn't it?

@junliume @JehandadKhan If you want to merge directly to the release branch, then please cherry-pick the same also into staging -- let's keep both in sync, so we'll be able to add more commits to staging and merge into release, if need arise.

Done for both release/rocm-rel-4.5-staging-verified (the one actually merged into release/rocm-rel-4.5) and release/rocm-rel-4.5-staging (the one has DB updates to remove solver 2c73a4f)

[atamazov]

@junliume Good!

Done for both release/rocm-rel-4.5-staging-verified (the one actually merged into release/rocm-rel-4.5)

I think we do not need release/rocm-rel-4.5-staging-verified branch anymore. This is just an ordinary branch that can be deleted after #1210 is merged in.

We can use the promotion procedure (directly from the staging branch) as discussed in mail.

[atamazov]

@junliume

Done for ... release/rocm-rel-4.5-staging (the one has DB updates to remove solver 2c73a4f)

I just cherry-picked #1211 is into release/rocm-rel-4.5-staging. Now 4.5 release staging has W/A for SWDEV-305815 identical to the one that resides in develop (the most "valid" one!), ready for promotion into 4.5 release, just in case if need arise.