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

NONEVM-745 solana schema #15171

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

Conversation

dhaidashenko
Copy link
Collaborator

@dhaidashenko dhaidashenko commented Nov 8, 2024

Resolves:

Copy link
Contributor

github-actions bot commented Nov 8, 2024

AER Report: Operator UI CI

aer_workflow , commit , Breaking Changes GQL Check

1. Workflow conclusion is failure:[convictional/trigger-workflow-and-wait@f69fa9e]

Source of Error:
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-26T14:45:25.4276506Z Checking conclusion [failure]
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-26T14:45:25.4277017Z Checking status [completed]
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-26T14:45:25.4277405Z Conclusion is not success, it's [failure].
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-26T14:45:25.4278282Z Propagating failure to upstream job

Why: The triggered workflow did not complete successfully. The conclusion status was "failure," which caused the upstream job to also fail.

Suggested fix: Investigate the logs of the downstream workflow (ID: 12033013585) to identify the specific reason for its failure and address the root cause.

AER Report: CI Core

aer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , Scheduled Run Frequency , 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 , Flakeguard Root Project / Run Tests , Flakeguard Root Project / Report , Flakey Test Detection , SonarQube Scan

1. Duplicate migration version found:go_core_race_tests

Source of Error:
Setup DB	2024-11-26T14:48:26.2734953Z migrateDB failed: failed to create goose provider: found duplicate migration version 259:
Setup DB	2024-11-26T14:48:26.2735902Z 	existing:0259_add_solana_schema.sql
Setup DB	2024-11-26T14:48:26.2736748Z 	current:0259_add_workflow_secrets.sql
Setup DB	2024-11-26T14:48:26.2788835Z ##[error]Process completed with exit code 1.

Why: The error occurred because there are two migration files with the same version number (259), which causes a conflict during the database migration process.

Suggested fix: Rename one of the migration files to have a unique version number to avoid conflicts.

2. Duplicate migration version found:go_core_tests_integration

Source of Error:
Setup DB	2024-11-26T14:47:36.2187274Z migrateDB failed: failed to create goose provider: found duplicate migration version 259:
Setup DB	2024-11-26T14:47:36.2188330Z 	existing:0259_add_solana_schema.sql
Setup DB	2024-11-26T14:47:36.2188850Z 	current:0259_add_workflow_secrets.sql
Setup DB	2024-11-26T14:47:36.2243479Z ##[error]Process completed with exit code 1.

Why: The error occurred because there are two migration files with the same version number (259), which causes a conflict during the database migration process.

Suggested fix: Rename one of the migration files to have a unique version number to avoid conflicts.

3. Duplicate migration version found:go_core_ccip_deployment_tests

Source of Error:
Setup DB	2024-11-26T14:47:46.1309101Z migrateDB failed: failed to create goose provider: found duplicate migration version 259:
Setup DB	2024-11-26T14:47:46.1310104Z 	existing:0259_add_solana_schema.sql
Setup DB	2024-11-26T14:47:46.1310580Z 	current:0259_add_workflow_secrets.sql
Setup DB	2024-11-26T14:47:46.1361941Z ##[error]Process completed with exit code 1.

Why: The error occurred because there are two migration files with the same version number (259), which causes a conflict during the database migration process.

Suggested fix: Rename one of the migration files to have a unique version number to avoid conflicts.

4. Duplicate migration version found:go_core_fuzz

Source of Error:
Setup DB	2024-11-26T14:47:34.9490409Z migrateDB failed: failed to create goose provider: found duplicate migration version 259:
Setup DB	2024-11-26T14:47:34.9491339Z 	existing:0259_add_solana_schema.sql
Setup DB	2024-11-26T14:47:34.9491779Z 	current:0259_add_workflow_secrets.sql
Setup DB	2024-11-26T14:47:34.9540031Z ##[error]Process completed with exit code 1.

Why: The error occurred because there are two migration files with the same version number (259), which causes a conflict during the database migration process.

Suggested fix: Rename one of the migration files to have a unique version number to avoid conflicts.

5. Duplicate migration version found:go_core_tests

Source of Error:
Setup DB	2024-11-26T14:48:11.7020990Z migrateDB failed: failed to create goose provider: found duplicate migration version 259:
Setup DB	2024-11-26T14:48:11.7022106Z 	existing:0259_add_solana_schema.sql
Setup DB	2024-11-26T14:48:11.7022898Z 	current:0259_add_workflow_secrets.sql
Setup DB	2024-11-26T14:48:11.7079382Z ##[error]Process completed with exit code 1.

Why: The error occurred because there are two migration files with the same version number (259), which causes a conflict during the database migration process.

Suggested fix: Rename one of the migration files to have a unique version number to avoid conflicts.

@reductionista
Copy link
Contributor

Strange that it seems to think the Operator UI is broken?

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