Bug #17926: spec/ruby/core/file/atime_spec.rb: a random failing test on Travis ppc64le

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN

[jaruga (Jun Aruga)]

I just observed the following test failing randomly on Travis ppc64le at the fd65ef2a5aa8629676d1edb6410e4d4cf60b8045. When running this commit on my forked repo, the test passed.

https://travis-ci.com/github/ruby/ruby/jobs/509310540#L2255

$ $SETARCH make -s test-spec MSPECOPT=-ff
...
1)
File.atime returns the last access time for the named file with microseconds FAILED
Expected 0 == 123456
to be truthy but was false
/home/travis/build/ruby/ruby/spec/ruby/core/file/atime_spec.rb:25:in `block (3 levels) in <top (required)>'
/home/travis/build/ruby/ruby/spec/ruby/core/file/atime_spec.rb:3:in `<top (required)>'

[jaruga (Jun Aruga)]

The failure happened on Travis ppc64le again yesterday.
https://travis-ci.com/github/ruby/ruby/jobs/510153529#L2250

[jaruga (Jun Aruga)]

I am trying to skip the test on Travis ppc64le for now.
https://github.com/ruby/ruby/pull/4546

[jaruga (Jun Aruga)]

Note that this failure was observed 4 days ago, at the build no #43628 - job number 509310540 first as far as I know. Since then, the failure rate is 4/35 = 11% so far.
https://www.travis-ci.com/github/ruby/ruby/builds

[jaruga (Jun Aruga)]

Note that this failure was observed 4 days ago, at the build no #43628 - job number 509310540 first as far as I know. Since then, the failure rate is 4/35 = 11% so far.

Ah. No. The 11% is not correct. Skipping the 4 builds after my PR to skip the failure in the past builds, the failure rate is 4/31 = 12% in the term.

[jeremyevans0 (Jeremy Evans)]

• Status changed from Open to Feedback

@jaruga (Jun Aruga) We haven't been seeing this error on the ppc64le RubyCI server recently. Is this OK to close?

[jaruga (Jun Aruga)]

• Status changed from Feedback to Closed

jeremyevans0 (Jeremy Evans) wrote in #note-5:

@jaruga (Jun Aruga) We haven't been seeing this error on the ppc64le RubyCI server recently. Is this OK to close?

@jeremyevans0 (Jeremy Evans) Yeah, it's ok to close.