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

Hashkey DF Soak #15814

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

Hashkey DF Soak #15814

wants to merge 2 commits into from

Conversation

amaechiokolobi
Copy link
Contributor

Requires

Supports

@amaechiokolobi amaechiokolobi requested review from a team as code owners December 29, 2024 20:09
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 Dec 29, 2024

AER Report: CI Core

aer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , Scheduled Run Frequency , Flakeguard Root Project / Get Tests To Run , Core Tests (go_core_tests) , GolangCI Lint (.) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_fuzz) , Core Tests (go_core_race_tests) , Flakeguard Deployment Project , test-scripts , Flakeguard Root Project / Run Tests , Flakeguard Root Project / Report , lint , SonarQube Scan , Flakey Test Detection

1. Request expired by executable client:[go_core_tests]

Source of Error:
client_test.go:42: 
	Error Trace:	/home/runner/work/chainlink/chainlink/core/capabilities/remote/executable/client_test.go:42
	 				/home/runner/work/chainlink/chainlink/core/capabilities/remote/executable/client_test.go:265
	 				/home/runner/work/chainlink/chainlink/core/capabilities/remote/executable/client_test.go:57
	 				/home/runner/work/chainlink/chainlink/core/capabilities/remote/executable/client_test.go:245
	 				/opt/hostedtoolcache/go/1.23.4/x64/src/runtime/asm_amd64.s:1700
	Error: 	Received unexpected error:
	 	error executing request: request expired by executable client
	Test: 	Test_Client_DonTopologies

Why: The error indicates that a request made by the executable client during the test Test_Client_DonTopologies expired before it could be completed. This could be due to network latency, a timeout setting that is too short, or the executable client not being able to process the request in time.

Suggested fix: Increase the timeout settings for the executable client in the test configuration. Additionally, investigate the performance of the executable client to ensure it can handle requests within the expected time frame.

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

@cl-sonarqube-production
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

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.

1 participant