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

chore: bump chainlink-protos/orchestrator #15343

Closed

Conversation

agparadiso
Copy link
Contributor

Requires

Supports

@agparadiso agparadiso force-pushed the CAPPL-217_expose_workflows_key_to_clo_bump branch from a5eb679 to ba2c9e7 Compare November 20, 2024 20:00
Copy link
Contributor

AER Report: CI Core

aer_workflow , commit , Clean Go Tidy & Generate , Detect Changes , 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) , lint , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , Find New Flaky Tests In Chainlink Project / Run Tests , Find New Flaky Tests In Chainlink Project / Report , Find New Flaky Tests In Deployment Project / Run Tests , Find New Flaky Tests In Deployment Project / Report , SonarQube Scan , Flakey Test Detection

1. Test failures encountered:[Run tests]

Source of Error:
Run tests	2024-11-20T20:16:30.5545683Z Encountered test failures.
Run tests	2024-11-20T20:16:30.5546369Z go_core_tests exiting with code 1
Run tests	2024-11-20T20:16:30.5564794Z ##[error]Process completed with exit code 1.

Why: The error indicates that the go_core_tests job encountered test failures during its execution. The exit code 1 is a standard indication of an error or failure in Unix-like systems.

Suggested fix: Review the test 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 for the tests to pass.

@agparadiso agparadiso closed this Nov 20, 2024
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