[#62297] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap. — Eric Wong <normalperson@...>
nari@ruby-lang.org wrote:
7 messages
2014/05/02
[#62307] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— SASADA Koichi <ko1@...>
2014/05/03
(2014/05/03 4:41), Eric Wong wrote:
[#62402] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— Eric Wong <normalperson@...>
2014/05/05
SASADA Koichi <ko1@atdot.net> wrote:
[#62523] [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan — ko1@...
Issue #9632 has been updated by Koichi Sasada.
3 messages
2014/05/11
[#62556] doxygen (Re: Re: [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan) — Tanaka Akira <akr@...>
2014-05-11 8:50 GMT+09:00 Eric Wong <normalperson@yhbt.net>:
3 messages
2014/05/13
[#62727] [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl — Eric Wong <normalperson@...>
rb_unlink_method_entry may cause old_me to be swept before the new
7 messages
2014/05/24
[#63039] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/10
Hi,
[#63077] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/10
SASADA Koichi <ko1@atdot.net> wrote:
[#63086] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/11
(2014/06/11 4:47), Eric Wong wrote:
[#63087] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/11
SASADA Koichi <ko1@atdot.net> wrote:
[#62862] [RFC] README.EXT: document rb_gc_register_mark_object — Eric Wong <normalperson@...>
Any comment on officially supporting this as part of the C API?
5 messages
2014/05/30
[ruby-core:62717] [ruby-trunk - Feature #9852] How to bundle test-unit2 and minitest5
From:
kou@...
Date:
2014-05-24 02:41:27 UTC
List:
ruby-core #62717
Issue #9852 has been updated by Kouhei Sutou.
Hiroshi SHIBATA wrote:
> I hope to bundle test-unit2 and minitest5 with Ruby 2.2.0.
Could you explain why you want to bundle test-unit2? It is for providing test-unit API. Right?
(test-unit API means that API provided by test-unit bundled in Ruby 1.8.)
If you expect that test-unit2 provides 100% compatible test-unit API, unfortunately it is wrong. test-unit2 has some incompatible API changes. For example, the following test suite shows different behavior:
```
require "test/unit"
class Parent < Test::Unit::TestCase
def test_parent
p :parent
end
class Child < self
def test_child
p :child
end
end
end
```
test-unit API (= test-unit gem 1.2.3) runs tests defined in parent test cases:
```
% ruby a.rb
Loaded suite a
Started
:parent
.:child
.:parent
.
Finished in 0.000207854 seconds.
3 tests, 0 assertions, 0 failures, 0 errors
```
test-unit2 doesn't run tests defined in parent test cases:
```
% ruby a.rb
Loaded suite a
Started
:parent
.:child
.
Finished in 0.001269378 seconds.
2 tests, 0 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed
1575.57 tests/s, 0.00 assertions/s
```
I think that the current test-unit2 behavior is better to write organized tests but it is not suitable for 100% compatible test-unit API expectation.
So I want you to explain why you want to bundle test-unit2.
> > kou
> Could you bundle and maintain test-unit2 on CRuby?
Yes with reservations. If bundling test-unit2 satisfies your expectation and it doesn't break integratioin with test-unit2 released at RubyGems.org(*), I say yes.
(*) Users couldn't use test-unit2 gem by `gem install test-unit`. Users also need to call `gem "test-unit"` in their code. It was solved by introducing default gem feature. I don't care about mechanism. It is OK to me that it is solved by other mechanism.
----------------------------------------
Feature #9852: How to bundle test-unit2 and minitest5
https://bugs.ruby-lang.org/issues/9852#change-46840
* Author: Hiroshi SHIBATA
* Status: Open
* Priority: Normal
* Assignee: Kouhei Sutou
* Category:
* Target version: current: 2.2.0
----------------------------------------
I removed test-unit and minitest at #9711
But we need to bundle testing framework with Ruby 2.2.0 continuously.
I hope to bundle test-unit2 and minitest5 with Ruby 2.2.0.
> kou
Could you bundle and maintain test-unit2 on CRuby?
> ryan
Do you have any idea of gem installation mechanism with packaging?
--
https://bugs.ruby-lang.org/