Skip to content

Expand review: suggest explanatory comment for the zero-seq guard #1107

Expand review: suggest explanatory comment for the zero-seq guard

Expand review: suggest explanatory comment for the zero-seq guard #1107

Triggered via push April 20, 2026 20:57
Status Failure
Total duration 14m 13s
Artifacts

tests.yaml

on: push
Lint
1m 18s
Lint
Build (Latest Go)
36s
Build (Latest Go)
Build (Minimum Go)
30s
Build (Minimum Go)
Sign-offs
13s
Sign-offs
Matrix: build-windows
Test Stores
9m 11s
Test Stores
Test JetStream
3m 28s
Test JetStream
Test Raft
8m 18s
Test Raft
Test JetStream Consumers
4m 42s
Test JetStream Consumers
Test JetStream Cluster 1
12m 31s
Test JetStream Cluster 1
Test JetStream Cluster 2
8m 35s
Test JetStream Cluster 2
Test JetStream Cluster 3
8m 20s
Test JetStream Cluster 3
Test JetStream Cluster 4
6m 16s
Test JetStream Cluster 4
Test JetStream Supercluster
6m 43s
Test JetStream Supercluster
Test No-Race 1
6m 46s
Test No-Race 1
Test No-Race 2
5m 18s
Test No-Race 2
Test MQTT
2m 44s
Test MQTT
Test Message Tracing
2m 24s
Test Message Tracing
Test JWT
5m 5s
Test JWT
Test Remaining Server Tests
5m 4s
Test Remaining Server Tests
Test Other Packages
5m 36s
Test Other Packages
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
Sign-offs
Process completed with exit code 1.
Sign-offs
Commit 1c2256eb049734ea1841872e28b745cd7cdb8ea3 has not been signed off in the commit message with a `Signed-off-by: Your Name <your.email@example.com>` line
Test JetStream
Process completed with exit code 1.
Test Remaining Server Tests
Process completed with exit code 1.
Test JetStream Cluster 4
Process completed with exit code 1.
Test Raft
Process completed with exit code 1.
Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: golangci/golangci-lint-action@1481404843c368bc19ca9406f87d6e0fc97bdcfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/