Investigate unstable widgets test

[talldan]

Description

This widgets test seems to be failing in trunk:
https://github.com/WordPress/gutenberg/runs/3014495507

FAIL specs/widgets/editing-widgets.test.js (114 s)
  ● Widgets screen › Should insert content using the inline inserter

    expect(received).toMatchInlineSnapshot(snapshot)

    Snapshot name: `Widgets screen Should insert content using the inline inserter 1`

    - Snapshot  - 9
    + Received  + 1

      Object {
    -   "sidebar-1": "<div class=\"widget widget_block widget_text\"><div class=\"widget-content\">
    - <p>First Paragraph</p>
    - </div></div>
    - <div class=\"widget widget_block\"><div class=\"widget-content\">
    - <h2>My Heading</h2>
    - </div></div>
    - <div class=\"widget widget_block widget_text\"><div class=\"widget-content\">
    - <p>Second Paragraph</p>
    - </div></div>",
    +   "wp_inactive_widgets": "",
      }

      374 | 		await saveWidgets();
      375 | 		const serializedWidgetAreas = await getSerializedWidgetAreas();
    > 376 | 		expect( serializedWidgetAreas ).toMatchInlineSnapshot( `
          | 		                                ^
      377 | 		Object {
      378 | 		  "sidebar-1": "<div class=\\"widget widget_block widget_text\\"><div class=\\"widget-content\\">
      379 | 		<p>First Paragraph</p>

      at Object.<anonymous> (specs/widgets/editing-widgets.test.js:376:35)

I couldn't see any artifacts for some reason.

[kevin940726]

I think there're no artifacts because the test completed, it just failed to match the snapshot. But I do expect it to generate some screenshots though. 🤔

[youknowriad]

I'm skipping two more e2e tests with similar failures here #33547

[youknowriad]

Another related failure #33875 in case anyone has an idea here.

[Mamaduka]

I spotted another e2e test failure, commenting here so we can keep an eye on it - https://github.com/WordPress/gutenberg/runs/3261461038.

[noisysocks]

@kevin940726: Was this fixed? Can we close the issue?

[kevin940726]

Nope, the test is skipped 7 months ago and hasn't been re-enabled yet 😅 . I think we can just re-enable it now that we have a flaky tests reporter and auto-retrying mechanism.

[jordesign]

@kevin940726 did this end up getting re-enabled?