Skip to content
CI

Fix sse-starlette event-loop binding in streaming tests (5 pre-existing failures) #13

Sign in to view logs

Fix sse-starlette event-loop binding in streaming tests (5 pre-existing failures)

Fix sse-starlette event-loop binding in streaming tests (5 pre-existing failures) #13

Triggered via pull request May 30, 2026 06:11
@FluffyAIcodeFluffyAIcode
opened #22
AgentMemory/streaming-tests-fix-8e7f
Status Success
Total duration 1m 44s
Artifacts 2

ci.yaml

on: pull_request
package import smoke
1m 32s
package import smoke
docker build + import smoke
1m 34s
docker build + import smoke
Matrix: unit tests + 100% coverage
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
package import smoke
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
docker build + import smoke
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit tests + 100% coverage (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
FluffyAIcode~Kakeya-LLM-Inference-engine~QIWPLL.dockerbuild
37 KB
sha256:55f0d818cc0e8a48af452ca06993d2bc359a5bb20638bd77e593b086c098b10e
coverage-py3.12 Expired
8.94 KB
sha256:bef66ee80347b39b7f4058224233d455dc0c3660cb986a54ea3020db7a2fdc91