[BUG] match-v5 "endOfGameResult": "Abort_Unexpected" for non aborted games

[geozukunft]

Bug Description
The endOfGameResult var in match-v5 (by-id) returns Abort_Unexpected for games that were concluded properly

Problem Description
Games that concluded correctly are falsly flagged as Abort_Unexpected

Expected Result
Not have Abort_Unexpected as the value for endOfGameResult games that weren't terminated by Vanguard

Actual Result
The matches did have Abort_Unexpected for games that weren't terminated

Developer Impact

I am reporting this on behalf of other devs. In general this seems to affect a larger amount of games especially in queue_id 420 and lets to miss categorization of games as terminated by Vanguard if one does not check additional fields. In general it is bad to have an unreliable field.

Player Impact
Depending on the different devs usescases this can falsify data of players.

Preconditions
This seems to have started sometime during June 11th likely with the deployment of the current patch

Issue Comments
As I am reporting this on behalf of other devs I don't have any match_ids as example atm either I'll followup later with some or someone else can post them here.

labels: api: match-v5 scope: lol type: unexpected behavior topic: underlying service (GAMHS)

[jsdt]

For some example match ids with this issue:

• SG2_31726207: other fields show that one team lost their nexus
• TW2_205251003: Other stats show this ended from a surrender
• RU_490603994: Another example where one team lost their nexus.

[rasm945i]

I also experience this. Heres a couple of the matches I noticed the bug in: NA1_5018382378 - gameEndedInSurrender is true, indicating the game finished correctly NA1_5018422066 - nexusKills is 1 for one of the participants, indicating the game finished correctly

[MingweiSamuel]

( #898 related for just the abort_unexpected data)