Skip to content

Conversation

@jmank88
Copy link
Contributor

@jmank88 jmank88 commented Feb 11, 2026

@jmank88 jmank88 force-pushed the BCF-3493-loopp-pprof branch from 2e8574a to 1d98288 Compare February 11, 2026 19:45
@github-actions
Copy link
Contributor

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

@cl-sonarqube-production
Copy link

Quality Gate failed Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarQube IDE SonarQube IDE

Copy link

@trunk-io trunk-io bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 Test Results: Unrelated Failure

Affected failures:

  1. Workflow Run: Integration Tests

What Broke

The loop.WebServerOpts service, introduced in the updated chainlink-common dependency and utilized in the refactored test, is not correctly handling its lifecycle within the test environment, leading to an unhandled error during execution. The CI failure is caused by the refactoring in core/web/loop_registry_test.go which introduces loop.WebServerOpts and servicetest.Run. The generic 'Process completed with exit code 1.' suggests that the loop.WebServerOpts service, as configured in the test, is failing to start or shut down cleanly when managed by servicetest.Run.

Autofix Options

You can use our MCP server to get AI assistance with debugging and fixing these failures.

  • Use MCP in your IDE to debug the issue. Try Help me fix CI failures from HfPEjBgc to get started.

Tip

Get Better Results: This CI job is not uploading test reports. Adding structured test reports enables more precise, test-level analysis with better root cause identification and more targeted fix recommendations.
👉🏻 Learn how to upload test results.

@trunk-io
Copy link

trunk-io bot commented Feb 11, 2026

Static BadgeStatic BadgeStatic BadgeStatic Badge

Failed Test Failure Summary Logs
TestBuildInfoController_Show_APICredentials The test for displaying API credentials in BuildInfoController failed to complete successfully. Logs ↗︎
TestCors_DefaultOrigins The test named TestCors_DefaultOrigins failed to complete successfully. Logs ↗︎
TestCosmosKeysController_Create_HappyPath The test for creating Cosmos keys did not complete successfully. Logs ↗︎
TestETHKeysController_ChainSuccess_Disable The test named 'TestETHKeysController_ChainSuccess_Disable' failed during execution. Logs ↗︎

... and 155 more

View Full Report ↗︎Docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant