[#80974] [Ruby trunk Feature#13517] [PATCH] reduce rb_mutex_t size from 160 to 80 bytes on 64-bit — ko1@...
Issue #13517 has been updated by ko1 (Koichi Sasada).
4 messages
2017/05/02
[#81024] Re: [Ruby trunk Feature#13517] [PATCH] reduce rb_mutex_t size from 160 to 80 bytes on 64-bit
— SASADA Koichi <ko1@...>
2017/05/07
sorry for late response.
[#80996] [Ruby trunk Feature#13544] Allow loading an ISeqs sequence directly from a C extension without requiring buffer is in an RVALUE — sam.saffron@...
Issue #13544 has been reported by sam.saffron (Sam Saffron).
3 messages
2017/05/04
[#81016] [Ruby trunk Bug#13526] Segmentation fault at 0x0055c2e58e8920 ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux] — s.wanabe@...
Issue #13526 has been updated by wanabe (_ wanabe).
3 messages
2017/05/07
[#81048] Re: [ruby-cvs:65788] normal:r58614 (trunk): rb_execution_context_t: move stack, stack_size and cfp from rb_thread_t — SASADA Koichi <ko1@...>
It causes compile error on raspi 3.
3 messages
2017/05/09
[#81201] Re: [ruby-cvs:65935] normal:r58761 (trunk): test/test_extilibs.rb: do not check the existence of fiddle — "U.NAKAMURA" <usa@...>
Hi, Eric
4 messages
2017/05/16
[#81202] Re: [ruby-cvs:65935] normal:r58761 (trunk): test/test_extilibs.rb: do not check the existence of fiddle
— Eric Wong <normalperson@...>
2017/05/16
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[#81427] Fwd: [ruby-changes:46809] normal:r58924 (trunk): test for IO.copy_stream CPU usage (r58534) — SASADA Koichi <ko1@...>
Hi,
6 messages
2017/05/28
[#81428] Re: Fwd: [ruby-changes:46809] normal:r58924 (trunk): test for IO.copy_stream CPU usage (r58534)
— Eric Wong <normalperson@...>
2017/05/28
SASADA Koichi <ko1@atdot.net> wrote:
[ruby-core:81057] Re: rapid CI service for MRI trunk
From:
Martin J. Dürst <duerst@...>
Date:
2017-05-09 06:58:31 UTC
List:
ruby-core #81057
Hello Koichi, Thanks for setting up this new service. On 2017/05/09 11:40, SASADA Koichi wrote: > Hi, > > I setup alternative CI server which aim to report rapid error detection. > > Features > (1) Got test results in minimum 2 min just after commit. > (2) Repeat tests many times. > (3) Sending alert mail > > Of course, RubyCI <http://rubyci.org/> is convenient because it shows > readable results. TravisCI is great service because we can test w/o > commit to trunk (master). > > This new CI aims to complement existing CI services. Is there a web interface to this service? I'm asking because I'd prefer to wait 2 minutes (on this new service) rather than up to 10 minutes (on TravisCI) to see whether a commit I make is successful. But I don't want to subscribe to the mailing list because I already get too many mails. Regards, Martin. > Features (details) > > (1) Got test results in minimum 2 min just after commit. > > RubyCI and TravisCI do > (a) svn checkout > (b) build from scratch > (c) run test (w/o parallelism on rubyci) > > But new CI do > (a) svn update > (b) build only updated (w/ -j[NPROC]) > (c) run test in (w/ -j[NPROC]) > > so that we can tests more rapidly. > > (2) Repeat tests many times. > > This CI system was implemented > > loop do > make up all install check test-rubyspec > if failure > make clean > alert > end > end > > # See all code > # https://github.com/ko1/build-ruby/blob/master/br.rb#L70 > > So that you can see not-frequent bugs, like GC/threading bugs. Actually, > I got about 30 alerts from this system yesterday. > > (3) Sending alert mail > > If there are failures, e-mail message is delivered. > > If you want to receive alert messages from this system by e-mail, please > join alert ML. > You only need to "Hi" to <ruby-alerts@quickml.atdot.net> with Cc > <ko1c-failure@atdot.net>. > > If someone commit broken patch, this system sends *hundreds* of alert > messages in hours. > > > Thanks, > Koichi Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>