Azure Pipelines / azure next.js
succeeded
Nov 15, 2023 in 31m 56s
Build #20231115.66 had test failures
Details
- Failed: 2 (0.57%)
- Passed: 322 (92.53%)
- Other: 24 (6.90%)
- Total: 348
Annotations
Check failure on line 1 in app dir - basic › <Link /> › should push to external url
azure-pipelines / azure next.js
app dir - basic › <Link /> › should push to external url
Test failed
Raw output
● app dir - basic › <Link /> › should push to external url
page.waitForSelector: Timeout 60000ms exceeded.
=========================== logs ===========================
waiting for locator('h1')
============================================================
362 | return this.chain(() => {
363 | return page
> 364 | .waitForSelector(selector, { timeout, state: 'attached' })
| ^
365 | .then(async (el) => {
366 | // it seems selenium waits longer and tests rely on this behavior
367 | // so we wait for the load event fire before returning
at waitForSelector (lib/browsers/playwright.ts:364:10)
Check failure on line 1 in app dir - basic › <Link /> › should replace to external url
azure-pipelines / azure next.js
app dir - basic › <Link /> › should replace to external url
Test failed
Raw output
● app dir - basic › <Link /> › should replace to external url
page.waitForSelector: Timeout 60000ms exceeded.
=========================== logs ===========================
waiting for locator('h1')
============================================================
362 | return this.chain(() => {
363 | return page
> 364 | .waitForSelector(selector, { timeout, state: 'attached' })
| ^
365 | .then(async (el) => {
366 | // it seems selenium waits longer and tests rely on this behavior
367 | // so we wait for the load event fire before returning
at waitForSelector (lib/browsers/playwright.ts:364:10)
Loading