Skip to content
CI

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

Sign in to view logs

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 #461

Triggered via pull request April 3, 2026 03:50
@dependabotdependabot[bot]
opened #99
dependabot/go_modules/modules/eventbus/go_modules-dae84125e0
Status Failure
Total duration 2m 47s
Artifacts 1

ci.yml

on: pull_request
Test
2m 44s
Test
Test CLI
47s
Test CLI
lint
20s
lint
Merge Unit/CLI/BDD Coverage
0s
Merge Unit/CLI/BDD Coverage
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 1 warning
lint
issues found
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.22s) - 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 expected queue length to be 3 (max size), got 4 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 suite.go:640: expected queue length to be 3 (max size), got 4 --- Failed steps: Scenario: Queue overflow handling with graceful degradation # features/eventlogger_module.feature:111 Then older events should be dropped from the queue # features/eventlogger_module.feature:114 Error: expected queue length to be 3 (max size), got 4 17 scenarios (16 passed, 1 failed) 93 steps (89 passed, 1 failed, 3 skipped) 5.215496064s --- FAIL: TestEventLoggerModuleBDD/Queue_overflow_handling_with_graceful_degradation (0.01s) - 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:aaf85c9532969125890a6f48a5eca4b23200b09b33f6130fe03b5714c872a469