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

Write Foundry Guide and update Solidity Style Guide #15199

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

Conversation

RensR
Copy link
Contributor

@RensR RensR commented Nov 12, 2024

No description provided.

@RensR RensR requested a review from a team as a code owner November 12, 2024 13:46
contracts/FOUNDRY_GUIDE.md Show resolved Hide resolved
contracts/STYLE_GUIDE.md Outdated Show resolved Hide resolved
@matYang
Copy link
Contributor

matYang commented Nov 13, 2024

nice foundry starter guide =)

Copy link
Contributor

github-actions bot commented Nov 13, 2024

AER Report: CI Core

aer_workflow , commit , Scheduled Run Frequency , Detect Changes , Clean Go Tidy & Generate , Find New Flaky Tests In Root Project / Find Tests To Run , lint , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Find New Flaky Tests In Deployment Project , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , Find New Flaky Tests In Root Project / Run Tests , Find New Flaky Tests In Root Project / Report , Flakey Test Detection , SonarQube Scan

1. Test failures encountered: [Run tests]

Source of Error:
Run tests	2024-11-14T12:57:22.1331242Z Exit code: 1
Run tests	2024-11-14T12:57:22.1331728Z Encountered test failures.
Run tests	2024-11-14T12:57:22.1333708Z go_core_tests exiting with code 1
Run tests	2024-11-14T12:57:22.1350871Z ##[error]Process completed with exit code 1.

Why: The error indicates that the Go core tests encountered failures, which caused the test suite 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 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.

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

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.

3 participants