test(napi/parser): increase timeout flag for fixture tests

[camc314]

I am still seeing this failure on some PRs

2025-10-07T17:20:30.0133725Z �[31m   �[31m�[31m fixtures�[2m > �[22mtarget/antd.js�[39m�[33m 5032�[2mms�[22m�[39m
2025-10-07T17:20:30.0133896Z �[31m     → Test timed out in 5000ms.
2025-10-07T17:20:30.0134434Z If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".�[39m

[camc314]

• test(napi/parser): increase timeout flag for fixture tests #14438 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull Request Overview

This PR increases the timeout for the "fixtures" test suite from the default 5000ms to 10000ms to address timeout failures occurring on some PRs during CI runs.

• Adds a timeout configuration of 10,000ms to the fixtures test suite

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[overlookmotel]

I think that's actually a different test from the one that was intermittently failing before.

The one I saw failing previously was "range & parent fixtures" which was added in #14344, whereas this test is "fixtures". Prior to #14344, this "fixtures" test never timed out, but now it does. My guess is that because the tests run concurrently, one test can slow down another, hence why unrelated changes can cause problems with a pre-existing test.

Anyway, I found that setting timeout option on the "range & parent fixtures" test didn't seem to do anything. Don't know why, but I just disabled the test completely in #14424. Probably we need to do the same here.

#14446 is an alternative to this PR which disables both the slow tests in CI.

[overlookmotel]

Superseded by #14446.