Only exclude the failing clocks for Process.clock_getres specs on AIX

* https://rubyci.org/logs/rubyci.s3.amazonaws.com/aix71_ppc/ruby-trunk/log/20190522T103301Z.fail.html.gz

2 files changed, 8 insertions, 1 deletions

diff --git a/spec/ruby/core/process/clock_getres_spec.rb b/spec/ruby/core/process/clock_getres_spec.rb
index 119e6ed680..0fc2a958b3 100644
--- a/spec/ruby/core/process/clock_getres_spec.rb
+++ b/spec/ruby/core/process/clock_getres_spec.rb
@@ -2,7 +2,7 @@ require_relative '../../spec_helper'
 require_relative 'fixtures/clocks'
 
 describe "Process.clock_getres" do
-  platform_is_not :freebsd, :aix do # clock_getres() seems incorrect on FreeBSD and AIX?
+  platform_is_not :freebsd do # clock_getres() seems incorrect on FreeBSD
     ProcessSpecs.clock_constants_for_resolution_checks.each do |name, value|
       it "matches the clock in practice for Process::#{name}" do
         times = []
diff --git a/spec/ruby/core/process/fixtures/clocks.rb b/spec/ruby/core/process/fixtures/clocks.rb
index 6e8a65f9de..7acc8fbd58 100644
--- a/spec/ruby/core/process/fixtures/clocks.rb
+++ b/spec/ruby/core/process/fixtures/clocks.rb
@@ -40,6 +40,13 @@ module ProcessSpecs
       }
     end
 
+    # These clocks in practice on AIX seem to be more precise than their reported resolution.
+    platform_is :aix do
+      clocks = clocks.reject { |clock, value|
+        [:CLOCK_REALTIME, :CLOCK_MONOTONIC].include?(clock)
+      }
+    end
+
     # On a Hyper-V Linux guest machine, these clocks in practice
     # seem to be less precise than advertised by clock_getres
     platform_is :linux do