mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
Skip File.atime
/File.mtime
tests randomly failing on Travis
Not only powerpc64le, also s390x and arm32 seem failing too. These failures are probably caused by filesystem settings on Travis, but unrelated to CPUs.
This commit is contained in:
parent
c3e37f74ae
commit
174ddc79c5
2 changed files with 11 additions and 9 deletions
|
@ -16,7 +16,7 @@ describe "File.atime" do
|
|||
end
|
||||
|
||||
platform_is :linux, :windows do
|
||||
platform_is_not :"powerpc64le-linux" do # https://bugs.ruby-lang.org/issues/17926
|
||||
unless ENV.key?('TRAVIS') # https://bugs.ruby-lang.org/issues/17926
|
||||
## NOTE also that some Linux systems disable atime (e.g. via mount params) for better filesystem speed.
|
||||
it "returns the last access time for the named file with microseconds" do
|
||||
supports_subseconds = Integer(`stat -c%x '#{__FILE__}'`[/\.(\d{1,6})/, 1], 10)
|
||||
|
|
|
@ -16,14 +16,16 @@ describe "File.mtime" do
|
|||
end
|
||||
|
||||
platform_is :linux, :windows do
|
||||
it "returns the modification Time of the file with microseconds" do
|
||||
supports_subseconds = Integer(`stat -c%y '#{__FILE__}'`[/\.(\d{1,6})/, 1], 10)
|
||||
if supports_subseconds != 0
|
||||
expected_time = Time.at(Time.now.to_i + 0.123456)
|
||||
File.utime 0, expected_time, @filename
|
||||
File.mtime(@filename).usec.should == expected_time.usec
|
||||
else
|
||||
File.mtime(__FILE__).usec.should == 0
|
||||
unless ENV.key?('TRAVIS') # https://bugs.ruby-lang.org/issues/17926
|
||||
it "returns the modification Time of the file with microseconds" do
|
||||
supports_subseconds = Integer(`stat -c%y '#{__FILE__}'`[/\.(\d{1,6})/, 1], 10)
|
||||
if supports_subseconds != 0
|
||||
expected_time = Time.at(Time.now.to_i + 0.123456)
|
||||
File.utime 0, expected_time, @filename
|
||||
File.mtime(@filename).usec.should == expected_time.usec
|
||||
else
|
||||
File.mtime(__FILE__).usec.should == 0
|
||||
end
|
||||
end
|
||||
end
|
||||
end
|
||||
|
|
Loading…
Reference in a new issue