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.

Sign up for GitHub

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

Jump to bottom

[Draft] Cusom sha damjan #15639

Draft
wants to merge 20 commits into
base: 2.19.0-dual-transmission
Choose a base branch
from
Draft

[Draft] Cusom sha damjan #15639

wants to merge 20 commits into from
+601 −156

Conversation

smickovskid
Copy link
Contributor

No description provided.

bolekk and others added 19 commits December 4, 2024 07:58
@bolekk
[KS-590] Auto-approval for workflow spec deletion (#15414)
b2427a7
@bolekk
[KS-590][bugfix] Auto-approval of workflow deletion - use correct ID (#…
3436729 
…15499)
@bolekk
Merge pull request #15505 from smartcontractkit/hotfix_deletion
7cfb885 
[KS-590] Auto-approval for workflow spec deletion
@Bwest981 @patrickhuie19
bumping wsrpc (#15549) (#15553)
600edee 
* bumping wsrpc (#15549)

* Update go.mod

* make gomodtidy

---------

Co-authored-by: Patrick <patrick.huie@smartcontract.com>
@bolekk
Increase default timeout of remote Executable requests (#15587)
8418784
@bolekk
Merge pull request #15600 from smartcontractkit/new_timeout_hotfix_br…
b2f7237 
…anch

Increase default timeout of remote Executable requests (#15587)
@krehermann
Ks 616/aptos hot fix (#15619)
02e67cb 
* isolate fix to mercury; more tests
@bolekk
[Keystone] Standard error message for remote execution errors (#15615)
7cf5b2f
@bolekk
Bump common to release/2.19.0-aptos branch
8df27e0
@bolekk
Merge pull request #15621 from smartcontractkit/release_error_logs_ho…
2b10a72 
…tfix

[Keystone] Standard error message for remote execution errors (#15615)
@bolekk
Merge branch 'release/2.19.0-aptos' into bump_common_2.19
d18ae90
@bolekk
Merge pull request #15625 from smartcontractkit/bump_common_2.19
36c0fc1 
Bump common to release/2.19.0-aptos branch
@patrickhuie19 @pkcll @bolekk
wiring engine histogram buckets through to beholder Client (#15508)
31cb374 
* wiring engine histogram buckets through to beholder Client

* bumping common

* Move metric views (#15515)

* bumping common

---------

Co-authored-by: Pavel <177363085+pkcll@users.noreply.github.com>
@patrickhuie19 @bolekk
fixing bug in labeler (#15406)
79d0047
@vyzaldysanchez @patrickhuie19 @bolekk
Add beholder metrics on workflow engine (#15238)
ea79473 
* Adds metrics on workflow engine

* Adds trigger event metric

* Removes comment

* metrics: execution duration histograms by status and removing now redundant instrumentation

* adding step execution time histogram

* fixing data race for global instruments

* cleanup + fixing tests

* renaming vars somehow fixes broken test

* removing short circuit in workferForStepRequest if Vertex call fails

* nil guard if Vertex errs

* updating workflow.name to workflow.hexName and fixing err log

---------

Co-authored-by: patrickhuie19 <patrick.huie@smartcontract.com>
@bolekk
Merge pull request #15626 from smartcontractkit/last3_release
ab4887c 
Hotfixes (histogram buckets + hex name + engine beholder metrics)
@graham-chainlink @archseer
fix(operator-ui): fix duplicate chain id in chain config dialog (#15585)
5c4c8a4 
There was an issue raised [here](https://chainlink-core.slack.com/archives/C06NF17JK9N/p1733437678773739?thread_ts=1733412322.287769&cid=C06NF17JK9N) impacting the chain config dialog of the operator ui, because the chain id is no longer unique now that we work with multichain, we need to handle it better by considering the network and chain id together instead of just chainid.

Context: smartcontractkit/operator-ui#97

JIRA: https://smartcontract-it.atlassian.net/browse/DPA-1384
@archseer
Merge branch 'release/2.19.0-aptos' into ui-fix-release-backport
1724a51
@bolekk
Merge pull request #15596 from smartcontractkit/ui-fix-release-backport
6daecb6 
fix(operator-ui): fix duplicate chain id in chain config dialog (#15585)
@smickovskid smickovskid changed the base branch from develop to 2.9.0-beta2 December 11, 2024 15:37
@smickovskid smickovskid changed the base branch from 2.9.0-beta2 to 2.19.0-dual-transmission December 11, 2024 15:38
@github-actions GitHub Actions
Copy link
Contributor

AER Report: CI Core

aer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , Scheduled Run Frequency , Find New Flaky Tests In Chainlink Project / Get Tests To Run , Find New Flaky Tests In Deployment Project / Get Tests To Run , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , lint , Core Tests (go_core_fuzz) , Find New Flaky Tests In Chainlink Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/capabilities/remote/executable/request, ... , Find New Flaky Tests In Chainlink Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/services/feeds, ubuntu-latest) , Find New Flaky Tests In Chainlink Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/services/ocr2/plugins/mercury, ubuntu-la... , Find New Flaky Tests In Chainlink Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/services/workflows, ubuntu-latest) , Find New Flaky Tests In Chainlink Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/capabilities/remote/executable, ubuntu-l... , Find New Flaky Tests In Deployment Project / Run Tests , Find New Flaky Tests In Deployment Project / Report , Find New Flaky Tests In Chainlink Project / Report , SonarQube Scan , Flakey Test Detection

1. Test failures encountered: go_core_tests

Source of Error: 
Run tests	2024-12-11T15:52:56.6744623Z Exit code: 1
Run tests	2024-12-11T15:52:56.6745132Z Encountered test failures.
Run tests	2024-12-11T15:52:56.6745915Z go_core_tests exiting with code 1
Run tests	2024-12-11T15:52:56.6765073Z ##[error]Process completed with exit code 1.

Why: The error indicates that the Go core tests encountered failures, which caused the process to exit with a non-zero status code (1). This is a common indication that one or more tests did not pass successfully.

Suggested fix: Review the test output logs to identify which specific tests failed and address the underlying issues in the code or test cases. Ensure all dependencies and configurations are correctly set up before re-running the tests.

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

@eutopian eutopian Awaiting requested review from eutopian eutopian will be requested when the pull request is marked ready for review eutopian is a code owner

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
8 participants
@smickovskid @bolekk @Bwest981 @krehermann @patrickhuie19 @vyzaldysanchez @graham-chainlink @archseer