Cannot find annotation point for Debug.LogError stack trace

[12joan]

Bug description

When a test fails due to a Debug.LogError message, results-parser.ts fails to parse the annotation point for its stack trace, which looks like this:

FMODUnity.RuntimeUtils:DebugLogError (string) (at Assets/Plugins/FMOD/src/RuntimeUtils.cs:580)
FMODUnity.RuntimeManager:DEBUG_CALLBACK (FMOD.DEBUG_FLAGS,intptr,int,intptr,intptr) (at Assets/Plugins/FMOD/src/RuntimeManager.cs:104)
FMOD.System:setOutput (FMOD.OUTPUTTYPE) (at Assets/Plugins/FMOD/src/fmod.cs:1048)
FMODUnity.RuntimeManager:Initialize () (at Assets/Plugins/FMOD/src/RuntimeManager.cs:330)
FMODUnity.RuntimeManager:get_Instance () (at Assets/Plugins/FMOD/src/RuntimeManager.cs:207)
FMODUnity.RuntimeManager:get_StudioSystem () (at Assets/Plugins/FMOD/src/RuntimeManager.cs:225)
FMODUnity.StudioListener:AddListener (FMODUnity.StudioListener) (at Assets/Plugins/FMOD/src/StudioListener.cs:72)
FMODUnity.StudioListener:OnEnable () (at Assets/Plugins/FMOD/src/StudioListener.cs:90)

How to reproduce

• Create a test that fails due to Debug.LogError
• In the GitHub workflow logs, see Warning: Not able to find annotation point for failed test!

Expected behavior

The annotation point should be parsed correctly, just as it is for exceptions.

Additional details

Related: #277