rspec-time-guard 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4bad43592a970ed079b0883df9ffe00474007e363c44647866721dc945a3fd89
-  data.tar.gz: 6f0c0134b10dc3305ad99bdfd7bb0074734371e5592162688dc1f5550d9c95b9
+  metadata.gz: d69f2e3a7c72240510df20aa4d415f38ef214b875e3e5158767b60f578e024f5
+  data.tar.gz: 79ed632e66858a540b9a73b3616477f43877f6a395e022a64de7959362a283d2
 SHA512:
-  metadata.gz: 775b1ddce8ca6055891d5b12db00d5e3b25aa40b4c6c14697f6231ed6e45b372ecf9db94666ab7a2d2c251a52a7ba9e0d81de85f48a132e900cd67d76da5dff8
-  data.tar.gz: e9097575f7a1d33c07fd339a68294d6b61c9c65397504ef556fc36740c2fde87e48cf154e3b3d50007b0642803476242fc88ca0c5b5f03584dcc5cd5d0745451
+  metadata.gz: c9dad05a04963ee2ca7bbb561cd219a99e03869fb42d5e77af3045e3ce4affccd8c606802682c48c2f30b925417ae80dc0cb65c0c8dc27246c8973887dcde3e1
+  data.tar.gz: 98c02103e8ae43889661e373c0544c60fd9fffee2e78f79049653bffdd3bf05b6721f38d053a7b51d2543822e6e58a75fe0a575159f4867441ebd022db867003

data/CHANGELOG.md

@@ -1,3 +1,9 @@
+## [0.2.1] - 2026-10-28
+- Use monotonic clock to prevent false timeouts with Timecop
+- Drop invalid `Exception` rescue clause
+- Remove useless logging from Railtie
+- Bump json dependency
+
 ## [0.2.0] - 2025-04-22
 - Experimental new implementation, using a single-threaded monitoring approach
 

data/README.md

@@ -1,7 +1,3 @@
-[//]: # (TODO: Add a public TODO list?)
-
-# ⚠️ **_This project is a Work In Progress_** ⚠️
-
 # RspecTimeGuard
 
 `RspecTimeGuard` monitors your tests as they run and provides safeguards against tests that take too long, helping you maintain a fast, reliable test suite.
@@ -171,8 +167,11 @@ RSpec Time Guard works by:
 3. Monitoring execution time
 4. Taking action if the time limit is exceeded
 
-### Performance Considerations
-> ⚠️ **Note**: Setting a global time limit with `global_time_limit_seconds` creates a monitoring thread for each test in your suite. This may result in slightly reduced performance, especially in large test suites. For optimal performance, you might consider applying time limits only to specific tests that are prone to slowness rather than setting a global limit.
+## Performance and Feedback
+
+RSpec Time Guard is a relatively new gem, and while our initial benchmarks show promising results, we're still gathering comprehensive performance data across different environments and use cases. The gem's impact on your test suite may vary depending on factors like test suite size, Ruby interpreter, and CI environment.
+
+I'd love to hear about your experience using RSpec Time Guard.
 
 ## Contributing
 

data/lib/rspec_time_guard/railtie.rb

@@ -3,11 +3,7 @@
 module RspecTimeGuard
   class Railtie < Rails::Railtie
     initializer "rspec_time_guard.configure" do
-      Rails.logger.info("INITIALIZER")
-
       config.after_initialize do
-        Rails.logger.info("AFTER INITIALIZE")
-
         if defined?(RSpec) && Rails.env.test?
           require "rspec_time_guard"
 

data/lib/rspec_time_guard/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module RspecTimeGuard
-  VERSION = '0.2.0'
+  VERSION = "0.2.1"
 end

data/lib/rspec_time_guard.rb

@@ -18,7 +18,7 @@ module RspecTimeGuard
       @mutex.synchronize do
         @active_tests[example.object_id] = {
           example: example,
-          start_time: Time.now,
+          start_time: Process.clock_gettime(Process::CLOCK_MONOTONIC),
           timeout: timeout,
           thread_id: thread.object_id,
           warned: false
@@ -52,7 +52,7 @@ module RspecTimeGuard
     end
 
     def check_for_timeouts
-      now = Time.now
+      now = Process.clock_gettime(Process::CLOCK_MONOTONIC)
       timed_out_examples = []
 
       @mutex.synchronize do
@@ -108,12 +108,11 @@ module RspecTimeGuard
       @_monitor ||= TimeoutMonitor.new
     end
 
+    # TODO: Write article (in 2 parts?)
     # TODO: check warnings on test suite
-    # TODO: run test suite with new implementation and compare perfs
-    # TODO: speed up test suite
-    #   => implement the 'single monitor thread' alternative
     # TODO: CHeck how it works with other Ruby interpreters? (check which implem was tested)
-    # TODO: Handle RSpec summary manually?
+    # TODO: Handle RSpec summary manually
+    #   -> Add a TimeGuard section
     # TODO: Run profiling on the whole test suite to check for performance issues
     def setup
       RSpec.configure do |config|
@@ -126,9 +125,6 @@ module RspecTimeGuard
 
           begin
             example.run
-          rescue RspecTimeGuard::TimeLimitExceededError => e
-            # NOTE: This changes the example's status to failed and records our error
-            example.exception = e
           ensure
             RspecTimeGuard.monitor.unregister_test(example)
           end

metadata

@@ -1,14 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: rspec-time-guard
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Lucas Montorio
-autorequire:
 bindir: exe
 cert_chain: []
-date: 2025-04-22 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -66,7 +65,6 @@ metadata:
   homepage_uri: https://github.com/LucasMontorio/rspec-time-guard
   source_code_uri: https://github.com/LucasMontorio/rspec-time-guard
   changelog_uri: https://github.com/LucasMontorio/rspec-time-guard/blob/main/CHANGELOG.md
-post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -81,8 +79,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.11
-signing_key:
+rubygems_version: 4.0.16
 specification_version: 4
 summary: A simple time keeper for RSpec tests.
 test_files: []