Skip to content
This repository has been archived by the owner on Aug 4, 2023. It is now read-only.

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

Open
jonoc330 opened this issue Jan 26, 2023 · 3 comments
Open

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

jonoc330 opened this issue Jan 26, 2023 · 3 comments

Comments

@jonoc330
Copy link

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

@tnolet
Copy link
Member

tnolet commented Jan 26, 2023

@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
Copy link
Member

tnolet commented Feb 8, 2023

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

@Antoine-C
Copy link

Antoine-C commented Feb 21, 2023

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
})

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants