1

JS parsing/compilation times not returned in webhook response

  • Live

N
Nick

It looks like JS parsing/compilation is considered when cpu.scriptEvaluation performance budget checks are performed.

This JS parsing/compilation is not returned from the webhook response so failures occur if cpu.scriptEvaluation is less than threshold but js parsing/compile time causes that threshold to be exceeded.

Is the JS parsing/compilation a sum of other values available from the webhook response, or is it just excluded from the response?

If excluded, please include it. I'm having a difficult enough time showing why a test fails based on the data returned, it's even harder when the data returned causes failures despite being below the configured threshold.

A

Activity Newest / Oldest

M

Matt

Status changed to: Live

M

Matt

Thanks for this request, the API/webhook data now also includes the `cpu.scriptParseCompile` metric.


  • N
N

Nick

Thanks for the quick fix! When can we expect to see this in the webhook response? As of this morning I'm not seeing it


M

Matt

It should be fixed now, I hadn't deployed the webhook code yet.


  • N
N

Nick

Confirmed, thanks for fixing this!