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

bump geth to v1.14.12 #15375

Draft
wants to merge 3 commits into
base: develop
Choose a base branch
from
Draft

bump geth to v1.14.12 #15375

wants to merge 3 commits into from

Conversation

jmank88
Copy link
Contributor

@jmank88 jmank88 commented Nov 21, 2024

It looks like params.Version was removed, so we will have to find a work around.

Copy link
Contributor

github-actions bot commented Nov 21, 2024

AER Report: CI Core

aer_workflow , commit , Detect Changes , Scheduled Run Frequency , Clean Go Tidy & Generate , Flakeguard Root Project / Get Tests To Run , lint , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , Flakeguard Deployment Project / Get Tests To Run , Flakeguard Root Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/bridges, ubuntu-latest) , Flakeguard Root Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/gethwrappers, ubuntu-latest) , Flakeguard Deployment Project / Run Tests , Flakeguard Deployment Project / Report , Flakeguard Root Project / Report , Flakey Test Detection , SonarQube Scan

1. Test failures encountered: go_core_tests

Source of Error:
Run tests	2024-11-22T20:54:26.4779814Z Encountered test failures.
Run tests	2024-11-22T20:54:26.4784607Z go_core_tests exiting with code 1
Run tests	2024-11-22T20:54:26.4797629Z ##[error]Process completed with exit code 1.

Why: The error indicates that the test suite go_core_tests encountered one or more test failures, which caused the process to exit with a non-zero status code (1).

Suggested fix: Review the test output logs to identify the specific tests that failed. Fix the underlying issues in the code or the tests themselves to ensure all tests pass.

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

RensR
RensR previously approved these changes Nov 22, 2024
@jmank88
Copy link
Contributor Author

jmank88 commented Nov 22, 2024

I thought that CI was just flaking, but this appears to legitimately break some log poller tests 🤔

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.

2 participants