[#60404] is RB_GC_GUARD needed in rb_io_syswrite? — Eric Wong <normalperson@...>
I haven't gotten it to crash as-is, but it seems like we need to
4 messages
2014/02/01
[#60682] volatile usages — Eric Wong <normalperson@...>
Hi all, I went ahead and removed some use of volatile which were once
5 messages
2014/02/13
[#60794] [RFC] rearrange+pack vtm and time_object structs — Eric Wong <normalperson@...>
Extracted from addendum on top of Feature #9362 (cache-aligned objects).
4 messages
2014/02/16
[#61139] [ruby-trunk - Feature #9577] [Open] [PATCH] benchmark/driver.rb: align columns in text output — normalperson@...
Issue #9577 has been reported by Eric Wong.
3 messages
2014/02/28
[ruby-core:60529] [ruby-trunk - Bug #9008] TestProcess#test_clock_getres_constants and TestProcess#test_clock_gettime_constants fails on ARM
From:
v.ondruch@...
Date:
2014-02-06 07:56:57 UTC
List:
ruby-core #60529
Issue #9008 has been updated by Vit Ondruch.
Just FYI, the test suite passes on Fedora Rawhide with 3.12.9-300.fc20.armv7hl Kernel. Thanks for pushing the fix upstream.
----------------------------------------
Bug #9008: TestProcess#test_clock_getres_constants and TestProcess#test_clock_gettime_constants fails on ARM
https://bugs.ruby-lang.org/issues/9008#change-44986
* Author: Vit Ondruch
* Status: Rejected
* Priority: Normal
* Assignee: Akira Tanaka
* Category:
* Target version:
* ruby -v: ruby -v: ruby 2.1.0dev (2013-09-22 trunk 43011) [armv7hl-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN
----------------------------------------
=begin
I observe following two errors on ARM Building Ruby for Fedora Rawhide. It seems that (({:CLOCK_REALTIME_ALARM})) and (({:CLOCK_BOOTTIME_ALARM})) are not supported there. The error message is confusing, though :/
3) Error:
TestProcess#test_clock_getres_constants:
Errno::E524: Unknown error 524 - clock_getres
/builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in `clock_getres'
/builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in `block in test_clock_getres_constants'
/builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in `each'
/builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in `test_clock_getres_constants'
4) Error:
TestProcess#test_clock_gettime_constants:
Errno::E524: Unknown error 524 - clock_gettime
/builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in `clock_gettime'
/builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in `block in test_clock_gettime_constants'
/builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in `each'
/builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in `test_clock_gettime_constants'
I am going to resolve the issue temporary by applying
sed -i '/Process.constants.grep(\/\\ACLOCK_\/).each {|n|/ s/$/\n next if [:CLOCK_REALTIME_ALARM, :CLOCK_BOOTTIME_ALARM].include? n/' \
test/ruby/test_process.rb
on ARM platform, but is there some better solution?
=end
--
http://bugs.ruby-lang.org/