test(fspy): benchmark tracking overhead#566
Conversation
Add a single multithreaded open-and-close workload, a Linux static variant, and three-platform Namespace reporting with PR/main baselines. Co-authored-by: GPT-5.6 Codex <codex@openai.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Make the reporter shell explicit and document why its text-only workflow_run boundary is intentionally safe. Co-authored-by: GPT-5.6 Codex <codex@openai.com>
Allow upload-artifact to include the dot-prefixed benchmark results directory. Co-authored-by: GPT-5.6 Codex <codex@openai.com>
Use a shorter process-level sampling window and inherit child stderr so runtime failures remain diagnosable. Co-authored-by: GPT-5.6 Codex <codex@openai.com>
Use pull-request write permission for the sticky benchmark report endpoint. Co-authored-by: GPT-5.6 Codex <codex@openai.com>
fspy benchmarkResults for commit LinuxCompared with previous PR run at
Workload: 4 threads, 2,048 files per thread, 8,192 total open-and-close operations.
MacosCompared with previous PR run at
Workload: 4 threads, 2,048 files per thread, 8,192 total open-and-close operations.
WindowsCompared with previous PR run at
Workload: 4 threads, 2,048 files per thread, 8,192 total open-and-close operations.
This comment is updated by the Fspy Benchmark workflow. |

Motivation
fspy does not have a stable cross-platform benchmark that isolates the wall-clock cost it adds to tracked child processes. A small synthetic workload makes regressions visible without introducing real-world repository variance.
Changes
LD_PRELOAD.main.workflow_runreporter.