-
Notifications
You must be signed in to change notification settings - Fork 98
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
main branch CI failed: schedule in Integration Tests on GCP #8422
Comments
GitHub Actions workflow Integration Tests on GCP #1404 failed. Event: workflow_dispatch Created by jayqi/failed-build-issue-action |
This was one was cancelled deliberately and replaced with https://github.com/ZcashFoundation/zebra/actions/runs/8904708364, see #8475 (comment) |
GitHub Actions workflow Integration Tests on GCP #1407 failed. Event: workflow_dispatch Created by jayqi/failed-build-issue-action |
Do we know why these are failing? There's 2 other "unexplained" ones |
GitHub Actions workflow Integration Tests on GCP #1512 failed. Event: schedule Created by jayqi/failed-build-issue-action |
Is this still an issue? I see we haven't had this happen for almost a month now |
Not an living issue, but an issue that I'm working on as it becomes a real issue everytime it happens, considering we have no visibility. |
GitHub Actions workflow Run tests #114 failed. Event: schedule Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #139 failed. Event: push Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #146 failed. Event: push Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #148 failed. Event: push Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #149 failed. Event: schedule Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #198 failed. Event: schedule Created by jayqi/failed-build-issue-action |
I need to check the Kubernetes logs issue, as those are not showing to fix this |
GitHub Actions workflow Run tests #316 failed. Event: push Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #319 failed. Event: push Created by jayqi/failed-build-issue-action |
1 similar comment
GitHub Actions workflow Run tests #319 failed. Event: push Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #338 failed. Event: workflow_dispatch Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #340 failed. Event: workflow_dispatch Created by jayqi/failed-build-issue-action |
We should prioritise this as it seems to be happening a lot lately |
We know why 4 of the 5 most recent failures happened and have fixed the issues (the cached states were updated with a database format change that wasn't backwards-compatible and there was a panic issue in one of the branches that was being tested), I'm not sure why the last one failed. |
We've pushed this to next sprint (Sprint 17) now |
GitHub Actions workflow Run tests #398 failed. Event: push Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #319 failed. Event: push Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #422 failed. Event: workflow_dispatch Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #316 failed. Event: push Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #441 failed. Event: push Created by jayqi/failed-build-issue-action |
GitHub Actions workflow Run tests #453 failed. Event: push Created by jayqi/failed-build-issue-action |
I'm closing this as the schedule one has been fixed, and this is issue is being updated with push events not related to the main issue, and most of them were fixed or were false/positives (fixed by re-running) |
GitHub Actions workflow Integration Tests on GCP #1323 failed.
Event: schedule
Branch: main
Commit: f1334a83789d49d374c8fe20729688d63bf76321
Created by jayqi/failed-build-issue-action
The text was updated successfully, but these errors were encountered: