Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure next/dist/compiled/react-dom is never treated as an external #64992

Closed
wants to merge 1 commit into from

Restore optimization

08818a2
Select commit
Loading
Failed to load commit list.
Closed

Ensure next/dist/compiled/react-dom is never treated as an external #64992

Restore optimization
08818a2
Select commit
Loading
Failed to load commit list.
Azure Pipelines / azure next.js succeeded Apr 24, 2024 in 31m 6s

Build #20240424.55 had test failures

0 errors / 0 warnings

Details

Tests

  • Failed: 4 (0.87%)
  • Passed: 430 (93.28%)
  • Other: 27 (5.86%)
  • Total: 461

Annotations

Check failure on line 1 in app dir - basic › known bugs › should support React fetch instrumentation › server component

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure next.js

app dir - basic › known bugs › should support React fetch instrumentation › server component 

Test failed
Raw output 
  ● app dir - basic › known bugs › should support React fetch instrumentation › server component

    page.waitForSelector: Timeout 60000ms exceeded.
    Call log:
      - waiting for locator('#value-1')

      421 |     return this.chain(() => {
      422 |       return page
    > 423 |         .waitForSelector(selector, { timeout, state: 'attached' })
          |          ^
      424 |         .then(async (el) => {
      425 |           // it seems selenium waits longer and tests rely on this behavior
      426 |           // so we wait for the load event fire before returning

      at waitForSelector (lib/browsers/playwright.ts:423:10)

Check failure on line 1 in app dir - basic › known bugs › should support React fetch instrumentation › server component client-navigation

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure next.js

app dir - basic › known bugs › should support React fetch instrumentation › server component client-navigation 

Test failed
Raw output 
  ● app dir - basic › known bugs › should support React fetch instrumentation › server component client-navigation

    page.waitForSelector: Timeout 10000ms exceeded.
    Call log:
      - waiting for locator('#value-1')

      421 |     return this.chain(() => {
      422 |       return page
    > 423 |         .waitForSelector(selector, { timeout, state: 'attached' })
          |          ^
      424 |         .then(async (el) => {
      425 |           // it seems selenium waits longer and tests rely on this behavior
      426 |           // so we wait for the load event fire before returning

      at waitForSelector (lib/browsers/playwright.ts:423:10)
      at Object.<anonymous> (e2e/app-dir/app/index.test.ts:1500:11)

Check failure on line 1 in app dir - basic › known bugs › should support React fetch instrumentation › server component

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure next.js

app dir - basic › known bugs › should support React fetch instrumentation › server component 

Test failed
Raw output 
  ● app dir - basic › known bugs › should support React fetch instrumentation › server component

    page.waitForSelector: Timeout 60000ms exceeded.
    Call log:
      - waiting for locator('#value-1')

      421 |     return this.chain(() => {
      422 |       return page
    > 423 |         .waitForSelector(selector, { timeout, state: 'attached' })
          |          ^
      424 |         .then(async (el) => {
      425 |           // it seems selenium waits longer and tests rely on this behavior
      426 |           // so we wait for the load event fire before returning

      at waitForSelector (lib/browsers/playwright.ts:423:10)

Check failure on line 1 in app dir - basic › known bugs › should support React fetch instrumentation › server component client-navigation

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure next.js

app dir - basic › known bugs › should support React fetch instrumentation › server component client-navigation 

Test failed
Raw output 
  ● app dir - basic › known bugs › should support React fetch instrumentation › server component client-navigation

    page.waitForSelector: Timeout 10000ms exceeded.
    Call log:
      - waiting for locator('#value-1')

      421 |     return this.chain(() => {
      422 |       return page
    > 423 |         .waitForSelector(selector, { timeout, state: 'attached' })
          |          ^
      424 |         .then(async (el) => {
      425 |           // it seems selenium waits longer and tests rely on this behavior
      426 |           // so we wait for the load event fire before returning

      at waitForSelector (lib/browsers/playwright.ts:423:10)
      at Object.<anonymous> (e2e/app-dir/app/index.test.ts:1500:11)
View more details on Azure Pipelines