2 tests failing
24/26 passing (92%)Timeout(2)
interrupt_request, shutdown_reply
Timeout failures often indicate the kernel doesn't implement certain message types. Check if these messages are supported in your kernel.
heartbeat_responds
Kernel responds to heartbeat ping within timeout
heartbeatPass
kernel_info_reply_valid
Kernel returns valid kernel_info_reply with status ok
kernel_info_requestPass
kernel_info_has_language_info
kernel_info_reply contains non-empty language_info.name
kernel_info_requestPass
kernel_info_has_protocol_version
kernel_info_reply contains non-empty protocol_version
kernel_info_requestPass
execute_stdout
Execute code that prints produces stream message on stdout
execute_requestPass
execute_stderr
Execute code that prints to stderr produces stream message
streamPass
execute_reply_ok
Execute valid code returns execute_reply with status ok
execute_requestPass
status_busy_idle_lifecycle
Kernel broadcasts busy then idle status on iopub during execution
statusPass
execute_input_broadcast
Kernel broadcasts execute_input on iopub when executing
execute_inputPass
shutdown_reply
Kernel responds to shutdown request and terminates cleanly
shutdown_requestFail
stdin_input_request
Kernel can request input from frontend via stdin channel
input_requestPass
comms_lifecycle
Kernel supports comm open/msg/close lifecycle
comm_openPass
interrupt_request
Kernel responds to interrupt request on control channel
interrupt_requestFail
execution_count_increments
Execution count increments with each execute_request
execute_requestPass
parent_header_correlation
All response messages contain correct parent_header
parent_headerPass