Disable flaky undo spec

[bytasv]

Since the spec randomly fails in CI, I've decided to disable it until I can find a way to fix it

[Janpot]

1. Why not leave it enabled, as a forcing function for us to fix?
2. Normally there is test.skip for this

edit

When I hover over page.waitForTimeout(600); I see:

Note that page.waitForTimeout() should only be used for debugging. Tests using the timer in production are going to be flaky. Use signals such as network events, selectors becoming visible and others instead.

Could be related?

[bytasv]

Why not leave it enabled, as a forcing function for us to fix?

I don't mind leaving it enabled. I'm currently working on this and trying to figure out why it's caused anyways (so no need for extra motivator to get this fixed). My main motivation of disabling it was to get rid of failing CI runs which can prevent other PRs from being merged. Given it takes ~15-20 mins for CI to run and fail personally for me this might be annoying, but if you are fine with it I definitely don't mind leaving it as is

Could be related?

Could be, I will try to mock timers if that's possible, but I need to actually WAIT without any signals, because that's the duration after throttle should be finished. Anyways, once I find the solution or find a root cause I will share it with the rest, maybe that's something to look for in the future as well 🤷

-edit: @Janpot I've changed comment out to use test.skip (for some reason I though that we have a lint rule which forbids using .skip..)

[Janpot]

Superseded by #1415