Skip to content

Process counts in lockfile, node_modules and cache variations don't start from each tool's own state; upm has no count #214

Closed

Description

@lukekarrys

Follow-up to #212 (process counts). In the lockfile, node_modules and cache variations, the process-count pass doesn't start any tool from its own state, the same problem #212 fixed for ci.

What happens

collect_process_count runs every tool's counted install one after another, with a single shared prepare. Whatever the variation's prepare doesn't clean is left by earlier tools, and the tool's own state never gets built:

clean is fine: its prepare resets everything.

Fix

Prepare each tool separately in these variations too, as ci now does with collect_process_count_per_pm (common.sh): each tool's counted run should start from the state its timed runs start from (its own lockfile, node_modules and cache, as the variation says), with nothing other tools left.

How to check it

In CI artifacts for these seven variations, process-count.json has all 10 tools on every fixture, and each count comes from a counted install that exited 0 and started from that tool's own state.

🤖 Generated with Claude Code

Activity

  1. changed the title [-]Process counts in lockfile variations don't start from each tool's own lockfile; upm has no count[/-] [+]Process counts in lockfile, node_modules and cache variations don't start from each tool's own state; upm has no count[/+] on Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions