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/extract
array
bignum
bug-3571
bug-5832
bug-14834
bug_reporter
class
cxxanyargs
debug
dln/empty
enumerator_kw
exception
fatal
file
float
funcall
gvl/call_without_gvl
hash
integer
iseq_load
iter
load
marshal
memory_status
memory_view
method
notimplement
num2int
path_to_class
popen_deadlock
postponed_job	Avoid assert failure when NULL EC is expected	2021-11-22 19:29:29 -05:00
printf
proc
random
rational
rb_call_super_kw
recursion
regexp
RUBY_ALIGNOF
scan_args
st
string
struct
symbol
thread_fd
time
tracepoint
typeddata
vm
wait
win32
auto_ext.rb