Alan Wu f5d2041138 Avoid assert failure when NULL EC is expected ... After 5680c38c75, postponed job APIs now expect to be called on native threads not managed by Ruby and handles getting a NULL execution context. However, in debug builds the change runs into an assertion failure with GET_EC() which asserts that EC is non-NULL. Avoid the assertion failure by passing `false` for `expect_ec` instead as the intention is to handle when there is no EC. Add a test from John Crepezzi and John Hawthorn to exercise this situation. See GH-4108 See GH-5094 [Bug #17573] Co-authored-by: John Hawthorn <john@hawthorn.email> Co-authored-by: John Crepezzi <john.crepezzi@gmail.com>		2021-11-22 19:29:29 -05:00
..
arith_seq
array
bignum
bug_reporter	Rename ::YJIT to RubyVM::YJIT	2021-10-28 13:43:02 -04:00
class
debug
exception
file
float
funcall
gvl
hash
integer
iseq_load
iter
load
marshal
method
num2int
path_to_class
popen_deadlock
postponed_job	Avoid assert failure when NULL EC is expected	2021-11-22 19:29:29 -05:00
proc
rational
st
string	[Feature #18239] Implement VWA for strings	2021-10-25 13:26:23 -04:00
struct
symbol
thread_fd
time
tracepoint
typeddata
vm
wait	fix random EBADF problem	2021-10-26 11:39:52 +09:00
win32
test_bug-3571.rb
test_bug-5832.rb
test_bug-14834.rb
test_enumerator_kw.rb
test_notimplement.rb
test_printf.rb
test_random.rb
test_recursion.rb
test_scan_args.rb