Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Txmv2 enablement #15286

Draft
wants to merge 70 commits into
base: txmv2
Choose a base branch
from
Draft

Txmv2 enablement #15286

wants to merge 70 commits into from

Conversation

dimriou
Copy link
Collaborator

@dimriou dimriou commented Nov 18, 2024

No description provided.

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.

🎖️ No JIRA issue number found in: PR title, commit message, or branch name. Please include the issue ID in one of these.

Copy link
Contributor

github-actions bot commented Nov 18, 2024

AER Report: CI Core

aer_workflow , commit , Clean Go Tidy & Generate , Detect Changes , Scheduled Run Frequency , GolangCI Lint (.) , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_fuzz) , Core Tests (go_core_race_tests) , test-scripts , lint , SonarQube Scan

1. Failed to execute capability:go_core_tests

Source of Error:
Run tests	2025-01-10T12:43:02.676Z	WARN	ExecutableCapabilityClient	request/client_request.go:200	received error response	{"version": "unset@unset", "error": "failed to execute capability"}
**Why**: The error indicates that the executable capability client received an error response indicating a failure to execute the capability. This could be due to a variety of reasons such as incorrect configuration, missing dependencies, or issues in the executable code.

Suggested fix: Check the configuration and dependencies of the executable capability. Ensure that all required components are correctly set up and that there are no issues in the executable code.

2. Received execution error:go_core_tests

Source of Error:
Run tests	2025-01-10T12:43:02.678Z	ERROR	ExecutableCapabilityServer.ServerRequest	request/server_request.go:238	received execution error	{"version": "unset@unset", "workflowExecutionID": "95ef5e32deb99a10ee6804bc4af13855687559d7ff6552ac6dbb2ce0abbadeed", "error": "8d1a3159-c0ef-4745-8b4f-7b0102aefde8"}
**Why**: The server received an execution error while processing a capability request. This error could be due to issues within the server's execution environment or the specific capability being executed.

Suggested fix: Investigate the specific error code or message ("8d1a3159-c0ef-4745-8b4f-7b0102aefde8") to understand the root cause. Check the server's execution environment and ensure that all necessary resources and permissions are available.

3. Request expired by executable client:go_core_tests

Source of Error:
Run tests	2025-01-10T12:43:18.7818342Z 	Error: 	Not equal: 
Run tests	2025-01-10T12:43:18.7819144Z 	 	expected: "error executing request: failed to execute capability"
Run tests	2025-01-10T12:43:18.7820086Z 	 	actual : "error executing request: request expired by executable client"
**Why**: The test expected an error message indicating a failure to execute the capability, but instead received an error message indicating that the request expired. This suggests a timeout issue where the executable client did not respond in time.

Suggested fix: Increase the timeout settings for the executable client or optimize the execution process to ensure it completes within the expected time frame. Additionally, investigate any potential performance bottlenecks that could be causing delays.

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

Copy link
Contributor

Flaky Test Detector for github.com/smartcontractkit/chainlink project has failed ❌

Ran new or updated tests between develop and d167c46 (txmv2_enablement).

View Flaky Detector Details | Compare Changes

Flaky Tests

Ran 639 unique tests. Below are the tests identified as flaky, with a pass ratio lower than the 99% threshold:

TestPackage                                                   TestName                                                                                                          PassRatio  RunCount   Skipped
---------                                                     ---------                                                                                                         ---------  ---------  ---------
github.com/smartcontractkit/chainlink/v2/core/chains/evm/txm  TestBroadcastTransaction/throws_a_warning_and_returns_if_unconfirmed_transactions_exceed_maxInFlightTransactions  33%        3          false
github.com/smartcontractkit/chainlink/v2/core/chains/evm/txm  TestLifecycle/tests_lifecycle_successfully_without_any_transactions                                               33%        3          false
github.com/smartcontractkit/chainlink/v2/core/chains/evm/txm  TestLifecycle                                                                                                     33%        3          false
github.com/smartcontractkit/chainlink/v2/core/chains/evm/txm  TestTrigger/Trigger_fails_if_Txm_is_unstarted                                                                     33%        3          false
github.com/smartcontractkit/chainlink/v2/core/chains/evm/txm  TestBroadcastTransaction                                                                                          33%        3          false
github.com/smartcontractkit/chainlink/v2/core/chains/evm/txm  TestTrigger                                                                                                       33%        3          false

Copy link
Contributor

Flakeguard Summary

Ran new or updated tests between develop and ec1be22 (txmv2_enablement).

View Flaky Detector Details | Compare Changes

Found Flaky Tests ❌

Name Pass Ratio Panicked? Timed Out? Race? Runs Successes Failures Skips Package Package Panicked? Avg Duration Code Owners
TestConfig_Validate 0.00% true false false 3 0 3 0 github.com/smartcontractkit/chainlink/v2/core/services/chainlink true 0s Unknown
TestConfig_Validate/invalid 0.00% true false false 3 0 3 0 github.com/smartcontractkit/chainlink/v2/core/services/chainlink true 0s Unknown

Artifacts

For detailed logs of the failed tests, please refer to the artifact failed-test-results-with-logs.json.

@dimriou dimriou changed the base branch from develop to txmv2 December 20, 2024 11:08
@dimriou dimriou force-pushed the txmv2 branch 2 times, most recently from 0fcdce8 to 6160f8f Compare January 3, 2025 05:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants