You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Process counts in lockfile, node_modules and cache variations don't start from each tool's own state; upm has no count #214
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:
Lockfile variations (lockfile, cache+lockfile, lockfile+node_modules, cache+lockfile+node_modules): lockfiles aren't cleaned between tools, so a tool finds earlier tools' lockfiles and not its own.
The other nine tools get counts, but not from the lockfile scenario the timed runs measure.
node_modules: a tool's counted run starts from the previous tool's node_modules, not its own.
cache: the tool's own cache is never warmed, so the "cache" count is really a cold-cache count (with other tools' caches around).
cache+node_modules: both of the above.
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.
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
Activity
[-]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[/+]