rspec-tracer 1.0.1 → 1.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 85f9e51c157fec46651a9276dd4b098d4ff749ef07efe66284b8c317b2b4d288
-  data.tar.gz: 676738fc078e588ac51233939274ed7245c9cdf41145dd86a2cdf7ce7068060d
+  metadata.gz: bd23aee4693655e787948be6a1e049f99942f8bf0b7f763dd7b2df9f04a01eec
+  data.tar.gz: a88e6daf316e8f35fecb6661a08c837470c7f0e3396d5e63522c29614e975d6e
 SHA512:
-  metadata.gz: c30eb3e54a8c19d7ad560cd03e860a12a9c5ead82a55af2b570e6a29737fb9c213a9ece0d0335b7882e8c65e851093e9f78710efe8df10e40fa54f01d2c84e51
-  data.tar.gz: fa0db0dd8257fc3841758fafbae04df2bd0abd64950b524ba3df10aace8a7965c11533d28dd78a51a4bfaf45dbdc34b634d48ccdce5b0c565a59ed3ee02cc7a1
+  metadata.gz: f9ab2ad270d188230c5d6eb82593055151dcb1f0d43d2c15fb15bab5d96876d8cae12f70c75eff7c80e81c6c53d8930812c173b5e67899f007237170b66deb9a
+  data.tar.gz: 9d3ce6ded81c0ce02a6a294d1317a732890ef3814a443e87c5345c65e316463e9266af701fe03520283cf58e1e7ecf9165d5ad45aa224e4f46f5410b0790394a

data/CHANGELOG.md

@@ -1,3 +1,63 @@
+## [1.0.3] - 2026-05-04
+
+### Fixed
+
+- **Carry-forward filter contract** — newly-added filters now apply
+  uniformly to both fresh attribution AND prior-snapshot carry-forward.
+  Previously, `Cache#load_all_files_cache` and `load_dependency_cache`
+  read previous-run state without re-applying the current filter list.
+  A user adding a new filter mid-development saw the filter take
+  effect only for fresh attributions on cold runs; previously-cached
+  paths matching the new filter persisted in `all_files` and
+  `dependency` until the next cold run. Filter additions now take
+  effect on the very next warm run. (from upstream
+  [PR #161](https://github.com/avmnu-sng/rspec-tracer/pull/161))
+
+### Note on exclusions
+
+The companion default-filter expansion shipped in upstream PR #161
+(adds `rspec_tracer_cache/`, `rspec_tracer_coverage/`,
+`rspec_tracer_report/`, `rspec_tracer.lock` to the default
+`add_filter` / `add_coverage_filter` lists) is intentionally NOT
+backported to this 1.0.x line, for the same reason the broader
+1.1.0 default-filter expansion was excluded from 1.0.1: changing
+the default filter set shifts the files present in `all_files.json`
+for users who track tracer-self paths, which would invalidate their
+existing caches on upgrade. Users on 1.0.x who want this default
+hygiene can either upgrade to 1.2.x / 2.0.x OR add the four paths
+to their own `.rspec-tracer` config explicitly. The carry-forward
+filter check shipped here MAKES that user-side `add_filter` take
+effect on the next warm run.
+
+## [1.0.2] - 2026-05-01
+
+### Fixed
+
+- **Parallel-tests merge silently dropped peer caches and left worker
+  directories behind** when the spawned-worker count exceeded
+  `ENV['PARALLEL_TEST_GROUPS']`. The merge + purge call-sites in
+  `lib/rspec_tracer.rb` (`merge_parallel_tests_reports`,
+  `merge_parallel_tests_coverage_reports`,
+  `purge_parallel_tests_reports`) iterated `1..ENV['PARALLEL_TEST_GROUPS']`
+  to construct per-worker directory names. But parallel_tests sets
+  `PARALLEL_TEST_GROUPS = num_processes.to_s` for each child, where
+  `num_processes` is the user-requested process count
+  (`Parallel.processor_count` by default) — not the actual worker
+  count. When `num_processes < spawned_worker_count` (e.g. when the
+  spec-count partition produces more non-empty groups than
+  `num_processes`, or shared-runner CPU detection drifts mid-run),
+  peer caches with `TEST_ENV_NUMBER` above the env bound were silently
+  dropped from the merge (warm-run skip decisions get made against
+  an under-sampled merged manifest) and left behind by the purge
+  (visible as straggler `parallel_tests_<N>/` directories under
+  `rspec_tracer_cache/`). The same gem behaviour was documented on
+  v1.1.1's `last_process?` fix
+  ([PR #101](https://github.com/avmnu-sng/rspec-tracer/pull/101)) but
+  the iteration call-sites kept the buggy bound. Each method now globs
+  the actual `parallel_tests_*` subdirectories under its base path,
+  making the merge + purge robust to whatever count parallel_tests
+  spawned. (from v1.2.1) No cache format change.
+
 ## [1.0.1] - 2026-04-24
 
 Long-tail maintenance release. Backports high-impact crash and correctness

data/lib/rspec_tracer/cache.rb

@@ -152,9 +152,10 @@ module RSpecTracer
 
       return unless File.file?(file_name)
 
-      @all_files = JSON.parse(File.read(file_name, encoding: 'UTF-8')).transform_values do |files|
+      raw = JSON.parse(File.read(file_name, encoding: 'UTF-8')).transform_values do |files|
         files.transform_keys(&:to_sym)
       end
+      @all_files = raw.reject { |fname, _| filtered_by_current_filters?(fname) }
     end
 
     def load_dependency_cache(cache_dir)
@@ -162,7 +163,18 @@ module RSpecTracer
 
       return unless File.file?(file_name)
 
-      @dependency = JSON.parse(File.read(file_name, encoding: 'UTF-8')).transform_values(&:to_set)
+      raw = JSON.parse(File.read(file_name, encoding: 'UTF-8')).transform_values(&:to_set)
+      @dependency = raw.transform_values do |files|
+        files.reject { |fname| filtered_by_current_filters?(fname) }.to_set
+      end
+    end
+
+    # True iff `file_name` matches any currently-configured filter.
+    # Applied at carry-forward seed time so newly-added filters take
+    # effect on the very next warm run instead of waiting for a cold
+    # run.
+    def filtered_by_current_filters?(file_name)
+      RSpecTracer.filters.any? { |f| f.match?(file_name: file_name) }
     end
 
     def load_examples_coverage_cache(cache_dir)

data/lib/rspec_tracer/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module RSpecTracer
-  VERSION = '1.0.1'
+  VERSION = '1.0.3'
 end

data/lib/rspec_tracer.rb

@@ -339,12 +339,7 @@ module RSpecTracer
       starting = Process.clock_gettime(Process::CLOCK_MONOTONIC)
       reports_dir = []
 
-      1.upto(ENV['PARALLEL_TEST_GROUPS'].to_i) do |test_num|
-        cache_path = File.dirname(RSpecTracer.cache_path)
-        cache_dir = File.join(cache_path, "parallel_tests_#{test_num}")
-
-        next unless File.directory?(cache_dir)
-
+      parallel_tests_peer_dirs(File.dirname(RSpecTracer.cache_path)).each do |cache_dir|
         run_id = JSON.parse(File.read(File.join(cache_dir, 'last_run.json'), encoding: 'UTF-8'))['run_id']
 
         reports_dir << File.join(cache_dir, run_id)
@@ -374,14 +369,8 @@ module RSpecTracer
       return unless parallel_tests_executed? && !simplecov?
 
       starting = Process.clock_gettime(Process::CLOCK_MONOTONIC)
-      reports_dir = []
 
-      1.upto(ENV['PARALLEL_TEST_GROUPS'].to_i) do |test_num|
-        coverage_path = File.dirname(RSpecTracer.coverage_path)
-        coverage_dir = File.join(coverage_path, "parallel_tests_#{test_num}")
-
-        reports_dir << coverage_dir if File.directory?(coverage_dir)
-      end
+      reports_dir = parallel_tests_peer_dirs(File.dirname(RSpecTracer.coverage_path))
 
       coverage_merger.merge(reports_dir)
 
@@ -410,13 +399,34 @@ module RSpecTracer
     def purge_parallel_tests_reports
       return unless parallel_tests_executed?
 
-      1.upto(ENV['PARALLEL_TEST_GROUPS'].to_i) do |test_num|
-        [RSpecTracer.cache_path, RSpecTracer.coverage_path, RSpecTracer.report_path].each do |path|
-          FileUtils.rm_rf(File.join(File.dirname(path), "parallel_tests_#{test_num}"))
+      [RSpecTracer.cache_path, RSpecTracer.coverage_path, RSpecTracer.report_path].each do |path|
+        parallel_tests_peer_dirs(File.dirname(path)).each do |worker_dir|
+          FileUtils.rm_rf(worker_dir)
         end
       end
     end
 
+    # Returns every `parallel_tests_*` subdirectory directly under
+    # `base_path`. Used by the parallel_tests merge + purge paths.
+    #
+    # Earlier patches iterated `1..ENV['PARALLEL_TEST_GROUPS'].to_i`
+    # to construct dir names, but parallel_tests's own runner sets
+    # PARALLEL_TEST_GROUPS to the user-requested process count
+    # (`Parallel.processor_count` by default), NOT the actual worker
+    # count. When num_processes < spawned_worker_count, the upper
+    # bound was too small: peer caches with TEST_ENV_NUMBER above the
+    # bound were silently dropped from the merge AND left behind by
+    # the purge. PR #101 (v1.1.1) documented this gem behaviour for
+    # `last_process?` detection but did not extend the fix to the
+    # iteration call-sites; this method closes that gap. Globbing the
+    # actual filesystem state is robust to the env discrepancy
+    # regardless of how the gem partitions specs.
+    def parallel_tests_peer_dirs(base_path)
+      Dir.glob(File.join(base_path, 'parallel_tests_*')).select do |path|
+        File.directory?(path)
+      end
+    end
+
     def parallel_tests_executed?
       return false unless parallel_tests? && parallel_tests_last_process?
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rspec-tracer
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.3
 platform: ruby
 authors:
 - Abhimanyu Singh
@@ -118,7 +118,7 @@ licenses:
 - MIT
 metadata:
   homepage_uri: https://github.com/avmnu-sng/rspec-tracer
-  source_code_uri: https://github.com/avmnu-sng/rspec-tracer/tree/v1.0.1
+  source_code_uri: https://github.com/avmnu-sng/rspec-tracer/tree/v1.0.3
   changelog_uri: https://github.com/avmnu-sng/rspec-tracer/blob/main/CHANGELOG.md
   bug_tracker_uri: https://github.com/avmnu-sng/rspec-tracer/issues
 rdoc_options: []