public-roadmap icon indicating copy to clipboard operation
public-roadmap copied to clipboard

Add trace data when a browser check times out at 120 seconds

Open jonoc330 opened this issue 3 years ago • 3 comments

I did request this via support but wanted to flag this here as it's probably a feature.

Unfortunately when a browser check times out at 120 seconds, there is no trace data for me to detect why this occurred. This is extremely frustrating as I can't replicate the timeouts on my local machine, and they only happen sporadically, see my monitoring results below.

Additional context Screenshot 2023-01-27 at 9 01 58 am

Screenshot 2023-01-27 at 8 59 40 am

jonoc330 avatar Jan 26 '23 22:01 jonoc330

@jonoc330 this is on our radar as we speak. We are looking at how to avoid this, or give you more actionable options to mitigate this.

tnolet avatar Jan 26 '23 23:01 tnolet

@jan-osch @Antoine-C do we have this on the radar?

tnolet avatar Feb 08 '23 18:02 tnolet

Hello @jonoc330,

Thanks for your feedback. Due to some internal limitations we can't output the trace nor videos on a check timeout. We noticed that the root cause for a lot of timing out checks comes from actions, so you can use the following to add a timeout to actions and your check should fail before the 120s limit. You'll have then traces and videos to help you understand what's going on.

const { test } = require('@playwright/test')

test.use({ actionTimeout: 10 * 1000 })

test('myTestCase', async ({ page }) => {
  // Test case
})

Antoine-C avatar Feb 21 '23 15:02 Antoine-C