Skip to content

core/services/workflows/v2: enforce PerWorkflow.ChainAllowed gate (#20548) [cherry-pick]#20601

Merged
jmank88 merged 1 commit intorelease/2.31.0-crefrom
2.31.0-cre-2bbb0de3a0846e1f034dc21aecf92029038afc15
Dec 11, 2025
Merged

core/services/workflows/v2: enforce PerWorkflow.ChainAllowed gate (#20548) [cherry-pick]#20601
jmank88 merged 1 commit intorelease/2.31.0-crefrom
2.31.0-cre-2bbb0de3a0846e1f034dc21aecf92029038afc15

Conversation

@jmank88
Copy link
Contributor

@jmank88 jmank88 commented Dec 11, 2025

…0548)

* core/services/workflows/v2: enforce PerWorkflow.ChainAllowed gate

* tools/bin/go_core_test: use -p 4 to reduce RAM
@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.

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. TestBuildProposalFromBatchesV2 (Workflow Run: Core Tests (go_core_ccip_deployment_tests))
  2. TestAddRemoteChainWithMcms (Workflow Run: Core Tests (go_core_ccip_deployment_tests))
  3. TestDeployMCMSWithTimelockV2 (Workflow Run: Core Tests (go_core_ccip_deployment_tests))
  4. TestConfigureForwarder (Workflow Run: Core Tests (go_core_ccip_deployment_tests))
  5. Workflow Run: Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_messaging_test.go:Test_CCIPMessaging_EVM2Solana
  6. Workflow Run: Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_messaging_test.go:Test_CCIPMessaging_Solana2EVM
  7. Workflow Run: Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_cs_rmn_curse_uncurse_test.go:TestRMNCurseConfigValidate
  8. Workflow Run: Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_cs_rmn_curse_uncurse_test.go:TestRMNCurseOneConnectedLanesSolana
  9. Workflow Run: Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_sui_messaging_test.go:Test_CCIP_Messaging_Sui2EVM
  10. Workflow Run: Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_cs_rmn_curse_uncurse_test.go:TestRMNUncurseBypass
  11. Workflow Run: Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_cs_rmn_curse_uncurse_test.go:TestRMNCurseOneConnectedLanes
  12. Workflow Run: Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_cs_rmn_curse_uncurse_test.go:TestRMNCurseOneConnectedLanesLaneOnlyOnSource
  13. Workflow Run: Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_token_transfer_test.go:*
  14. Workflow Run: Integration Tests

What Broke

These failures appear to be unrelated to the changes in this PR. The majority are caused by transient external network or service issues, such as TLS handshake timeouts and HTTP 503 Service Unavailable errors from GitHub, which prevented the download of necessary release artifacts (e.g., Solana, chainlink-ccip, SUI). Additionally, some failures are due to known test flakiness or unhandled errors from new gate limiting logic.

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 pKMoVy5W to get started.

View all test uploads

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: Go Test Parallelism Reduced

Affected failures:

  1. Workflow Run: Integration Tests

What Broke

The reduction of concurrent Go test packages to 4 in the go_core_tests script caused the integration tests to fail.

Proposed Fixes

Remove the lines that limit test parallelism in the go_core_tests script.

In go_core_tests:17

- # Temporary reduction in concurrent packages to reduce RAM usage
- GO_TEST_FLAGS="$GO_TEST_FLAGS -p=4"
Autofix Options

You can apply the proposed fixes directly to your branch. Try the following:

  • Comment /trunk stack-fix INjvpxne to generate a stacked PR with the proposed fixes.
  • Use MCP in your IDE to fix the issue. Try Help me fix CI failures from INjvpxne 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.

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: Dependency Incompatibility, Solana

Affected tests:

  1. TestSetConfigMCMSV2Solana (Workflow Run: Core Tests (go_core_ccip_deployment_tests))
  2. TestValidateConfigureTokenPoolContractsForSolana (Workflow Run: Core Tests (go_core_ccip_deployment_tests))

What Broke

Updates to the github.com/smartcontractkit/chainlink-common dependency introduced incompatibilities. These led to issues such as HTTP client failures (503 status code) when downloading Solana artifacts and malformed account data during Solana Timelock program initialization.

Proposed Fixes

Add a User-Agent header to HTTP requests for Solana artifact downloads to improve compatibility with GitHub's release server, and update the chainlink-ccip module to a compatible version, then synchronize go.mod and go.sum.

go get -u github.com/smartcontractkit/chainlink-ccip
go mod tidy

In artifacts.go:116

 \tif err != nil {
 \t	return err
 \t}
+ \treq.Header.Set("User-Agent", "chainlink-artifact-downloader/1.0")

 \tres, err := (&http.Client{}).Do(req)
 \tif err != nil {
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 cojHITFh to get started.

View all test uploads

@trunk-io
Copy link

trunk-io bot commented Dec 11, 2025

Static BadgeStatic BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

@jmank88 jmank88 enabled auto-merge (squash) December 11, 2025 17:17
@jmank88 jmank88 requested a review from HashWrangler December 11, 2025 17:17
@jmank88 jmank88 merged commit bf0ce48 into release/2.31.0-cre Dec 11, 2025
509 of 546 checks passed
@jmank88 jmank88 deleted the 2.31.0-cre-2bbb0de3a0846e1f034dc21aecf92029038afc15 branch December 11, 2025 17:24
@cl-sonarqube-production
Copy link

Quality Gate failed Quality Gate failed

Failed conditions
4.34% Technical Debt Ratio on New Code (required ≤ 4%)

See analysis details on SonarQube

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.

3 participants