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 5 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-15T03:09:38.6352156Z Checking conclusion [failure]
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-15T03:09:38.6353017Z Checking status [completed]
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-15T03:09:38.6354117Z Conclusion is not success, it's [failure].
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-15T03:09:38.6355106Z Propagating failure to upstream job
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-15T03:09:38.7712588Z ##[debug]Docker Action run completed with exit code 1

Why: The triggered workflow concluded with a failure status, which caused the upstream job to fail as well. The exact reason for the failure is not detailed in these logs but is indicated by the propagated failure status.

Suggested fix: Investigate the logs of the triggered workflow (ID: 11849529841) at the provided URL to identify the specific cause of the failure and address it accordingly.

AER Report: CI Core ran successfully ✅

aer_workflow , commit

@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