Jupyter Kernel Conformance

Protocol compliance test results for Jupyter kernels

Last tested February 27, 2026 at 06:27 PMbec63f4
Back to Matrix

xcpp17

xeus-cling (c++) • Protocol 5.3

View on GitHub

13 tests failing

13/26 passing (50%)
Timeout(4)
comm_info_request, display_data, update_display_data +1 more
Protocol error: Failed to deliver message (6 frames) cause of Not connected to peers. Unable to send messages(3)
comms_lifecycle, execution_count_increments, parent_header_correlation
Protocol error: Codec Error: Broken pipe (os error 32)(2)
execute_result, shutdown_reply
inspect_reply status: Error(1)
inspect_request
Protocol error: Error deserializing content for msg_type `history_reply`: data did not match any variant of untagged enum HistoryEntry(1)
history_request

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
heartbeat
Pass
kernel_info_reply_valid
Kernel returns valid kernel_info_reply with status ok
kernel_info_request
Pass
kernel_info_has_language_info
kernel_info_reply contains non-empty language_info.name
kernel_info_request
Pass
kernel_info_has_protocol_version
kernel_info_reply contains non-empty protocol_version
kernel_info_request
Pass
execute_stdout
Execute code that prints produces stream message on stdout
execute_request3ms
Pass
execute_stderr
Execute code that prints to stderr produces stream message
stream2ms
Pass
execute_reply_ok
Execute valid code returns execute_reply with status ok
execute_request
Pass
status_busy_idle_lifecycle
Kernel broadcasts busy then idle status on iopub during execution
status
Pass
execute_input_broadcast
Kernel broadcasts execute_input on iopub when executing
execute_input
Pass
shutdown_reply
Kernel responds to shutdown request and terminates cleanly
shutdown_request
Fail

complete_request
Kernel responds to completion request with complete_reply
complete_request8ms
Pass
inspect_request
Kernel responds to inspection request with inspect_reply
inspect_request22ms
Fail
is_complete_complete
Kernel correctly identifies complete code as 'complete'
is_complete_request
Pass
is_complete_incomplete
Kernel correctly identifies incomplete code as 'incomplete'
is_complete_request
Pass
history_request
Kernel responds to history request with history_reply
history_request1ms
Fail
comm_info_request
Kernel responds to comm_info request with comm_info_reply
comm_info_request10001ms
Fail
error_handling
Kernel properly reports errors for invalid syntax
execute_request2ms
Pass

display_data
Kernel can produce display_data messages for rich output
display_data10036ms
Fail
update_display_data
Kernel can update existing displays via update_display_data
update_display_data10015ms
Fail
execute_result
Expression evaluation produces execute_result on iopub
execute_result
Fail
rich_execute_result
Expression evaluation produces execute_result with rich MIME types (HTML, images, etc.)
execute_result
Skip

stdin_input_request
Kernel can request input from frontend via stdin channel
input_request
Skip
comms_lifecycle
Kernel supports comm open/msg/close lifecycle
comm_open
Fail
interrupt_request
Kernel responds to interrupt request on control channel
interrupt_request10000ms
Fail
execution_count_increments
Execution count increments with each execute_request
execute_request
Fail
parent_header_correlation
All response messages contain correct parent_header
parent_header
Fail