Skip to content

build(deps): bump the go_modules group across 2 directories with 2 updates #465

build(deps): bump the go_modules group across 2 directories with 2 updates

build(deps): bump the go_modules group across 2 directories with 2 updates #465

Status Failure
Total duration 2m 55s
Artifacts 1

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 1 warning
lint
issues found
lint: feeders/dot_env.go#L19
File is not properly formatted (gofmt)
lint: feeders/base_config.go#L21
File is not properly formatted (gofmt)
lint: feeders/affixed_env.go#L32
File is not properly formatted (gofmt)
lint: contract_verifier.go#L180
do not define dynamic errors, use wrapped static errors instead: "fmt.Errorf(\"HealthCheck panicked: %v\", r)" (err113)
lint: contract_verifier.go#L133
do not define dynamic errors, use wrapped static errors instead: "fmt.Errorf(\"Reload panicked: %v\", r)" (err113)
lint: application.go#L742
do not define dynamic errors, use wrapped static errors instead: "fmt.Errorf(\"panic initializing module %s: %v\", name, r)" (err113)
Failed Test: TestEventLoggerModuleBDD: eventlogger/bdd_test_runner_test.go#L0
TestEventLoggerModuleBDD: === RUN TestEventLoggerModuleBDD Feature: Event Logger Module As a developer using the Modular framework I want to use the event logger module for structured event logging So that I can track and monitor application events across multiple output targets bdd_test_runner_test.go:134: non-zero status returned, failed to run feature tests --- FAIL: TestEventLoggerModuleBDD (5.05s) - No trace available
Failed Test: TestEventLoggerModuleBDD/Queue_overflow_handling_with_graceful_degradation: eventlogger/bdd_test_runner_test.go#L0
TestEventLoggerModuleBDD/Queue_overflow_handling_with_graceful_degradation: === RUN TestEventLoggerModuleBDD/Queue_overflow_handling_with_graceful_degradation Scenario: Queue overflow handling with graceful degradation # features/eventlogger_module.feature:111 Given I have an event logger module configured with queue overflow testing # bdd_test_runner_test.go:119 -> *EventLoggerBDDTestContext When I emit more events than the queue can hold before start # bdd_test_runner_test.go:120 -> *EventLoggerBDDTestContext Then older events should be dropped from the queue # bdd_test_runner_test.go:121 -> *EventLoggerBDDTestContext And newer events should be preserved in the queue # bdd_test_runner_test.go:122 -> *EventLoggerBDDTestContext When the eventlogger starts # bdd_test_runner_test.go:114 -> *EventLoggerBDDTestContext Then only the preserved events should be processed # bdd_test_runner_test.go:123 -> *EventLoggerBDDTestContext expected preserved event queue.overflow.event3 not found in logs. Found queue overflow events: []. Total logs: 21 suite.go:640: expected preserved event queue.overflow.event3 not found in logs. Found queue overflow events: []. Total logs: 21 --- Failed steps: Scenario: Queue overflow handling with graceful degradation # features/eventlogger_module.feature:111 Then only the preserved events should be processed # features/eventlogger_module.feature:117 Error: expected preserved event queue.overflow.event3 not found in logs. Found queue overflow events: []. Total logs: 21 17 scenarios (16 passed, 1 failed) 93 steps (92 passed, 1 failed) 5.050240999s --- FAIL: TestEventLoggerModuleBDD/Queue_overflow_handling_with_graceful_degradation (0.23s) - No trace available
Test
Process completed with exit code 1.
Test
Process completed with exit code 1.
Test CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/

Artifacts

Produced during runtime
Name Size Digest
cli-coverage Expired
13.1 KB
sha256:d867edb172beb677dfd59db4381691b89f2d12fd629508c095af1a0ffe52e59d