-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
base: develop
Are you sure you want to change the base?
NONEVM-745 solana schema #15171
Conversation
AER Report: Operator UI CIaer_workflow , commit , Breaking Changes GQL Check 1. Workflow conclusion is failure:[convictional/trigger-workflow-and-wait@f69fa9e]Source of Error:
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 Coreaer_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_testsSource of Error:
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_integrationSource of Error:
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_testsSource of Error:
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_fuzzSource of Error:
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_testsSource of Error:
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. |
Strange that it seems to think the Operator UI is broken? |
Resolves: