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

CTFv2 PoC test #14865

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

CTFv2 PoC test #14865

wants to merge 55 commits into from

Conversation

skudasov
Copy link
Collaborator

No description provided.

@skudasov skudasov changed the title Ctf v2 tests CTFv2 PoC test Oct 21, 2024
Copy link
Contributor

github-actions bot commented Oct 22, 2024

AER Report: CI Core

aer_workflow , commit , Clean Go Tidy & Generate , Detect Changes , Scheduled Run Frequency , 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) , Core Tests (go_core_race_tests) , Find New Flaky Tests In Deployment Project , 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. Uncommitted changes detected:[Ensure clean after generate]

Source of Error:
Ensure clean after generate	2024-11-07T16:50:38.6587603Z go.md | 3 +++
Ensure clean after generate	2024-11-07T16:50:38.6588136Z 1 file changed, 3 insertions(+)
Ensure clean after generate	2024-11-07T16:50:38.9262435Z ##[error]Process completed with exit code 1.

Why: The error occurred because there were uncommitted changes in the repository after running the generate command. The git diff --stat --exit-code command detected modifications in the go.md file.

Suggested fix: Ensure that all changes are committed before running the generate command or modify the generate command to not alter tracked files.

AER Report: Operator UI CI

aer_workflow , commit , Breaking Changes GQL Check

1. Workflow conclusion is failure: [Breaking Changes GQL Check]

Source of Error:
2024-11-07T16:42:50.4775672Z Checking conclusion [failure]
2024-11-07T16:42:50.4776563Z Checking status [completed]
2024-11-07T16:42:50.4778233Z Conclusion is not success, it's [failure].
2024-11-07T16:42:50.4779063Z Propagating failure to upstream job

Why: The triggered workflow did not complete successfully. The status check returned a conclusion of "failure," which caused the upstream job to fail as well.

Suggested fix: Investigate the logs of the downstream workflow (ID: 11727412718) to identify the specific cause of failure. Address the root cause in the downstream workflow to ensure it completes successfully.

@skudasov skudasov requested a review from a team as a code owner October 30, 2024 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants