test: absolute time bounds and other flakes under load (server, parallel suites)

Open
#436 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript

Research direction

Start by listing tests that use absolute wall-clock bounds across the core, mcp, server, and pivotkit-report workspaces. Read the timing-test changes in #421 and #423, then run the affected suites in parallel to reproduce flakes. Update each test to use ratio bounds or interleaved best-of-N rounds while confirming it still fails on the defect it was written to detect.

Written by the indexing model from the issue text.

Description

area:tests

When all 8 workspaces' test suites run at the same time (harder than npm test, which runs them one after another), other tests with absolute time bounds fail now and then. Example: pivotkit-report "hostile markup ... in linear time" took 1046 ms against a 1 s bound. Tests in core, mcp and server failed occasionally as well.

This is the same pattern that #421 fixed for the xlsx used-range test. The CI runs one workspace at a time, so this has not caused a red main.

Fix: list the tests that use absolute wall-clock bounds. Move them to ratio bounds or interleaved best-of-N rounds, as in #423, without loosening what they detect: each must still fail on the defect it was written for.

Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
3h 21m
Merged PRs (30d)
250

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eizedev/pivotkit

All issues in eizedev/pivotkit

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.