[#87773] timer thread [was Re: [ruby-alerts:7905] failure alert on trunk-asserts@silicon-docker (NG (r63844))] — Eric Wong <normalperson@...>
> test_all <main>: warning: pthread_create failed for timer: Resource temporarily unavailable, scheduling broken
[#87836] [Ruby trunk Bug#14898] test/lib/test/unit/parallel.rb: TestSocket#test_timestamp stuck sometimes — ko1@...
Issue #14898 has been reported by ko1 (Koichi Sasada).
[email protected] wrote:
On 2018/07/06 18:47, Eric Wong wrote:
[#87847] undefined symbol: mjit_init_p — Leam Hall <leamhall@...>
I pulled Ruby trunk on 3 Jul and am now getting errors similar to the
QXMgSSB0b2xkIHlvdSwgYG1ha2UgaW5zdGFsbGAgaXMgbmVlZGVkIHRvIG1ha2UgUnVieSB3b3Jr
T25lIG1vcmUgcmVhc29uIGZvciBodHRwczovL2J1Z3MucnVieS1sYW5nLm9yZy9pc3N1ZXMvMTM2
[#87986] [Ruby trunk Feature#14915] Deprecate String#crypt, move implementation to string/crypt — mame@...
Issue #14915 has been updated by mame (Yusuke Endoh).
[email protected] wrote:
normalperson (Eric Wong) wrote:
[#88088] [Ruby trunk Misc#14937] [PATCH] thread_pthread: lazy-spawn timer-thread only on contention — normalperson@...
Issue #14937 has been reported by normalperson (Eric Wong).
[#88104] [Ruby trunk Bug#14898] test/lib/test/unit/parallel.rb: TestSocket#test_timestamp stuck sometimes — ko1@...
Issue #14898 has been updated by ko1 (Koichi Sasada).
[#88173] [Ruby trunk Bug#14950] r64109 thread.c: move ppoll wrapper before thread_pthread.c - Windows compile failure - thread.c — Greg.mpls@...
Issue #14950 has been reported by MSP-Greg (Greg L).
[#88189] [Ruby trunk Bug#14950] r64109 thread.c: move ppoll wrapper before thread_pthread.c - Windows compile failure - thread.c — nobu@...
Issue #14950 has been updated by nobu (Nobuyoshi Nakada).
[#88199] [Ruby trunk Misc#14937] [PATCH] thread_pthread: lazy-spawn timer-thread only on contention — takashikkbn@...
Issue #14937 has been updated by k0kubun (Takashi Kokubun).
[email protected] wrote:
> yet, sky3 had a failure at
> http://ci.rvm.jp/results/trunk@P895/1173951
> > http://ci.rvm.jp/results/trunk@P895/1173951
[ruby-core:87850] [Ruby trunk Misc#14861] DevelopersMeeting20180718Japan
Issue #14861 has been updated by k0kubun (Takashi Kokubun). * [Bug #14878] Add command line argument to deactivate JIT (k0kubun) * Please discuss the necessity of the flag and its name in the proposal. ---------------------------------------- Misc #14861: DevelopersMeeting20180718Japan https://bugs.ruby-lang.org/issues/14861#change-72868 * Author: naruse (Yui NARUSE) * Status: Open * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- Date: 2018/07/18 (Thu) Time: 14:00-18:00 (JST) Place: MoneyForward HQ (beware: new location) (Tokyo, Japan) Sign-up: https://ruby.connpass.com/event/92314/ log: https://docs.google.com/document/d/1_cKh0LJd18y5CH1MfM6WC1fqh2rpHHZntrBCLTbwRSE/edit pub: https://docs.google.com/document/d/1_cKh0LJd18y5CH1MfM6WC1fqh2rpHHZntrBCLTbwRSE/pub Please comment your favorite ticket numbers you want to ask to discuss with your *SHORT* comment or summary. (your summary/comment will help us because we don't need to read all of ticket comments) *DO NOT* discuss then on this ticket, please. From this time, we use a ticket to make dev-meeting agenda page instead of a wiki page <https://bugs.ruby-lang.org/projects/ruby/wiki#Developer-Meetings>. # NOTE Dev meeting *IS NOT* a decision making place. All decisions should be done at the bug tracker. Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly. Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue). We will write a log about discussion to a file or to each ticket in English. All activities are best-effort (keep in mind that most of us are volunteer developers). The date, time and place is scheduled according to when/where we can reserve Matz's time. # Agenda ## Next dev-meeting ## About 2.6 timeframe ## From Attendees (will be edited later) (if you have a write access permission, please list directly) * [Feature #13881] Use getcontext/setcontext on OS X * [Bug #14847] `clone` can generate strange objects * we found several strange behavior so let's clear the specification * [Feature #13625] BigDecimal short form / shorthand * mrkn: BigDecimal is not a core class, so we cannot add such a syntax sugar. * [Bug #14858] Introduce 2nd GC heap named Transient heap (ko1) * introduce new memory management technique. * [Bug #14699] Subtle behaviors with endless range (mame) * Need to be discussed with mrkn * [Bug #14845] Endless Range with nil (mame) * Should explicit nil for endless range (like (1..nil)) be prohibited or not? * [Bug #14824] Endless Range Support in irb (aycabta) * [Feature #14808] Last token of endless range should have EXPR_END (aycabta) ## From non-attendees (will be edited later) (if you have a write access, please list directly) * [Feature #14781] Enumerator#generate (zverok) * more reasonable version of Object#enumerate proposed for the previous meeting. * [Feature #14830] RubyVM::MJIT.pause / RubyVM::MJIT.resume (k0kubun) * Is it okay to add such methods? If so, is there any comment for the behavior described in the ticket? * [Feature #14709] Proper pattern matching (zverok) * [Feature #14799] Startless range (zverok) * [Feature #14784] One-sided Comparable#clamp (with endless/startless ranges) (zverok) * [Feature #14859] Timeout in VM (normalperson) * Still needs some work, mainly wondering if the idea of moving this part of stdlib into core VM is acceptable or not. No semantic changes except speed improvement. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>