TST: Skip flaky offset test case on WASM

[mroeschke]

e.g. https://github.com/pandas-dev/pandas/actions/runs/11661309317/job/32465371369

Not sure why this case is failing only on WASM, but IMO let's just skip this narrow case to get a clearer green signal

[jorisvandenbossche]

Can we reproduce the case with a non-hypothesis written out test case? (or extract that from the failure logs using reproduce_failure>)
Because it might still be worth keeping track of it somewhere in case someone has time to look into it or knows more about it.

But agreed to skip this for now to get green CI.

[jorisvandenbossche]

Maybe ideally open an issue about it with the reproducer and add a link to that issue here?

[mroeschke]

Opened up #60205 to track this failure. I wasn't able to locally reproduce this on OSX.

(I suspect that for the Pyodide build we should install tzdata and avoid having the build look at the system timezone)

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 2.3.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 eea95a304795d5c0e72494a645af417e0449bc9f

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #60186: TST: Skip flaky offset test case on WASM'

4. Push to a named branch:

git push YOURFORK 2.3.x:auto-backport-of-pr-60186-on-2.3.x

5. Create a PR against branch 2.3.x, I would have named this PR:

"Backport PR #60186 on branch 2.3.x (TST: Skip flaky offset test case on WASM)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.