celld/tck

Test results

Complete
Run #107 ↗mainf6f0b0e7Attempt 1
Results303 / 303
Passed291
Accepted exceptions12

3 divergences · 9 known bugs

Failed / missing0

0 failed · 0 missing

Suites

success: Capacity5 passed · 5 scheduled

Job: success

Download report JSON ↓

tck-e3ca5dd9-d2ae-4cf0-979a-974b33edfcf7

success: celld104 passed · 116 scheduled

Job: success

Download report JSON ↓

tck-382ea877-0747-4c5c-a6d6-b256b098528d

success: Dependencies6 passed · 6 scheduled

Job: success

Download report JSON ↓

tck-40689e07-fcbe-4d87-b93f-3e00f7272077

success: Faults22 passed · 22 scheduled

Job: success

Download report JSON ↓

tck-3719eb89-26ec-44a2-87ac-cb250cc450cf

success: Fleet5 passed · 5 scheduled

Job: success

Download report JSON ↓

tck-647356e8-16f0-4b1f-aaf8-f5ff31d59d99

success: Multinode4 passed · 4 scheduled

Job: success

Download report JSON ↓

tck-80a81a5d-45e6-4b9e-a0be-a4a7eb95c34f

success: Operations6 passed · 6 scheduled

Job: success

Download report JSON ↓

tck-e3ec9061-3249-43fa-ac3b-1db8a7447faf

success: Recovery6 passed · 6 scheduled

Job: success

Download report JSON ↓

tck-f3112433-0c5f-4551-be3f-5e4e3666a9fe

success: Reference110 passed · 110 scheduled

Job: success

Download report JSON ↓

tck-e01ef8c7-4e19-4206-a8cc-9559dcb6335e

success: Resilience10 passed · 10 scheduled

Job: success

Download report JSON ↓

tck-f8985a01-2131-4d38-920a-0c6e9a2b3c1e

success: Security5 passed · 5 scheduled

Job: success

Download report JSON ↓

tck-eca11ebd-f634-4b6d-aed8-e5d85be2d376

success: Static & unitFormatting · lint · types · unit tests

Job: success

success: Telemetry5 passed · 5 scheduled

Job: success

Download report JSON ↓

tck-a504a8f5-6658-4c4c-a200-cda5f292b9f6

success: Traffic3 passed · 3 scheduled

Job: success

Download report JSON ↓

tck-9698f4f1-2aad-4251-ab2b-e90025f06cf4

Test matrix 195

Download results
195 casesClick a result for details
Case / contractSuiteReference workerd × 2Candidate celld
alarmsfire↗API compatibility
alarmsrearm-pending-timer↗API compatibility
alarmsretry↗API compatibility
alarmsset-replace-delete↗API compatibility
assetsbinding↗API compatibility
assetshtml-routing↗API compatibility
assetsredirects↗API compatibility
assetsroot-worker-first↗API compatibility
assetsworker-first↗API compatibility
cachedocumented-miss↗API compatibility
concurrencyexplicit-gate↗API compatibility
concurrencyinput-gates↗API compatibility
contextexports-fetch↗API compatibility
contextwait-until↗API compatibility
cryptoaes-gcm↗API compatibility
cryptoecdsa-p256↗API compatibility
cryptoed25519↗API compatibility
cryptoinvalid-input↗API compatibility
cryptokey-derivation↗API compatibility
cryptokey-export↗API compatibility
cryptosha256-hmac↗API compatibility
cryptox25519↗API compatibility
d1batch-rollback↗API compatibility
d1bindings-results↗API compatibility
d1exec-batch↗API compatibility
deploymentinvalid-nameAPI compatibility—
deploymentlegacy-migrationAPI compatibility—
deploymentmissing-classAPI compatibility—
deploymentroutesAPI compatibility—
deploymentunsupported-bindingAPI compatibility—
deploymentvalid-configAPI compatibility—
dynamicbindings↗API compatibility
dynamicfetch↗API compatibility
dynamiclimits↗API compatibility
dynamicoutbound↗API compatibility
dynamicprops↗API compatibility
dynamicrelative-imports↗API compatibility
dynamicvalidation↗API compatibility
dynamicwasm-shape↗API compatibility
facetsexports-class↗API compatibility
facetsisolation↗API compatibility
facetsoutbound-transaction↗API compatibility
facetstransaction↗API compatibility
flagsdisabled-counterparts↗API compatibility
flagsenabled-defaults↗API compatibility
httpabort↗API compatibility
httpbody-consumption↗API compatibility
httpencoding↗API compatibility
httpfetch-abort↗API compatibility
httpheaders↗API compatibility
httpredirect↗API compatibility
httprequest-response↗API compatibility
httpunicode-headers↗API compatibility
httpurl-formdata↗API compatibility
identitynamespace↗API compatibility
kvbinary-pagination↗API compatibility
kvexpiration↗API compatibility
kvmetadata-list↗API compatibility
kvstream-limit↗API compatibility
kvstream-put↗API compatibility
messagingevent-source↗API compatibility
messagingmessage-channel↗API compatibility
nodeassert↗API compatibility
nodeasync-context↗API compatibility
nodebuffer↗API compatibility
nodehash-compression↗API compatibility
nodepath-events↗API compatibility
nodestream-timers↗API compatibility
nodeutil↗API compatibility
queuesbatch-ack-retry↗API compatibility
queuesretry-delay↗API compatibility
r2conditional-write↗API compatibility
r2key-identity↗API compatibility
r2list-options↗API compatibility
r2metadata-range-delete↗API compatibility
r2multipart↗API compatibility
reprobody-readers↗API compatibilityNot scheduledNot scheduled
reprostorage-errors↗API compatibilityNot scheduledNot scheduled
rpcnamed-service↗API compatibility
rpcreturned-target↗API compatibility
rpcstructured-clone↗API compatibility
rpcthrown-error↗API compatibility
sqlbindings-cursors↗API compatibility
sqlconstraints↗API compatibility
sqlconsumed-write-cursor↗API compatibility
sqlinvalid-utf8↗API compatibility
sqlmixed-rollback↗API compatibility
sqlnested-sync↗API compatibility
sqlopen-read-cursor↗API compatibility
sqltransaction-commit↗API compatibility
sqltransaction-rollback↗API compatibility
storagebatch-ranges↗API compatibility
storagedelete-all↗API compatibility
storageexplicit-rollback↗API compatibility
storageinvalid-input↗API compatibility
storagerich-values↗API compatibility
storageround-trip↗API compatibility
storagesync-committed↗API compatibility
storagesynchronous-kv↗API compatibility
storagetransaction-commit↗API compatibility
storagetransaction-rollback↗API compatibility
streamsbackpressure↗API compatibility
streamscancel↗API compatibility
streamserror↗API compatibility
streamshttp-binary↗API compatibility
streamstee↗API compatibility
streamstransform↗API compatibility
wasmmodule↗API compatibility
webhtml-rewriter↗API compatibility
websocketconcurrent-sockets↗API compatibility
websockethandler-streaming↗API compatibility
websocketoutbound-close↗API compatibility
websocketpeer-close↗API compatibility
websocketprotocol-attachment↗API compatibility
workflowsevent↗API compatibility
workflowsretry↗API compatibility
workflowssteps-sleep-result↗API compatibility
workflowstimeout↗API compatibility
capacityinsufficient-spareQualification—
capacitylarge-restoreQualification—
capacitymemory-pressureQualification—
capacityqueue-loadQualification—
capacityslow-consumerQualification—
dependencieshibernationQualification—
dependenciesqueue-acceptanceQualification—
dependenciesqueue-redeliveryQualification—
dependenciessocket-failoverQualification—
dependenciesstream-reconnectQualification—
dependenciesworkflow-recoveryQualification—
faultsgate-deadlineQualification—
faultspeer-partitionQualification—
faultsreload-adoptionQualification—
faultsreload-forcedQualification—
faultsreload-in-flightQualification—
faultsreload-invalidQualification—
faultsreload-module-bytesQualification—
faultsreload-socketQualification—
faultsrolling-deploymentQualification—
faultsstorage-ambiguousQualification—
faultsstorage-latencyQualification—
faultsstorage-throttleQualification—
faultsstorage-timeoutQualification—
faultssync-abortQualification—
faultssync-barrier-partitionQualification—
faultssync-outageQualification—
faultssync-recoveryQualification—
faultssync-transactionQualification—
faultstransaction-deadlineQualification—
faultswrite-cursor-outboundQualification—
faultswrite-cursor-responseQualification—
faultswrite-cursor-syncQualification—
operationsbinary-upgradeQualification—
operationsconcurrent-drainQualification—
operationsgraceful-drainQualification—
operationspreserve-reloadQualification—
operationsrebalance-controlQualification—
operationsweighted-placementQualification—
securitybody-limitsQualification—
securityforwarded-headersQualification—
securitylistener-separationQualification—
securitypeer-authenticationQualification—
securityreserved-classesQualification—
telemetrycli-devQualification—
telemetrycli-operatorQualification—
telemetryexport-isolationQualification—
telemetryparquet-exportQualification—
telemetrytrace-contextQualification—
trafficcrash-ledgerQualification—
trafficpaused-ownerQualification—
trafficrestart-racesQualification—
fleetfollower-recoveryRecovery & resilience—
fleetowner-failoverRecovery & resilience—
fleetowner-rejoinRecovery & resilience—
fleetroutingRecovery & resilience—
fleetstorage-partitionRecovery & resilience—
multinodeowner-failoverRecovery & resilience—
multinodeowner-rejoinRecovery & resilience—
multinoderoutingRecovery & resilience—
multinodestorage-partitionRecovery & resilience—
recoverycrashRecovery & resilience—
recoverydisk-lossRecovery & resilience—
recoveryfacetsRecovery & resilience—
recoverygracefulRecovery & resilience—
recoveryoverdue-alarmRecovery & resilience—
recoverystorage-outageRecovery & resilience—
resiliencefollower-lossRecovery & resilience—
resiliencefollower-recoveryRecovery & resilience—
resilienceinterrupted-writesRecovery & resilience—
resilienceowner-failoverRecovery & resilience—
resilienceowner-rejoinRecovery & resilience—
resiliencepaused-ownerRecovery & resilience—
resiliencereplica-disk-lossRecovery & resilience—
resilienceroutingRecovery & resilience—
resiliencesimultaneous-restartRecovery & resilience—
resiliencestorage-partitionRecovery & resilience—
PassDivergenceKnown bugFailNo report— Not applicable
Scope and exclusions

Public API behavior on the pinned local workerd and celld releases. A representative contract corpus, not an exhaustive proof for every input or distributed schedule.

Local validation only. AWS unqualified. Test design ↗

AWS provisioning and distributed recovery

AWS remains unqualified. Local distributed fault scenarios run separately in the recovery, multinode, fleet, resilience, and qualification suites; they are not API differential cases.

Containers, Sandbox, and edge-only services

Require a separate container runtime or managed Cloudflare environment; not implied by the local celld container.

Cron, TCP/TLS, and managed Cloudflare service guarantees

Require a clock-controlled or externally reachable reference environment; not established by Miniflare API emulation. Miniflare has no scheduler and celld v0.5.0 exposes no scheduled trigger, so cron has no shared triggering mechanism; TLS certificate validation needs a publicly trusted certificate neither runtime can be given locally. See RUNTIME-BREADTH.md.

PITR

PITR-specific controls are not implemented. WebSocket hibernation is tested separately by dependencies.hibernation, with actual eviction and a surviving socket. Multi-node routing is covered by the multinode, fleet, and resilience suites.

Diagnostic repros

Run separately with the repros suite; excluded from default CI.

Download suite report ↓