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

Bridge Update Papercuts 10/02/23 #646

Open
47 of 67 tasks
guineveresaenger opened this issue Oct 3, 2023 · 1 comment
Open
47 of 67 tasks

Bridge Update Papercuts 10/02/23 #646

guineveresaenger opened this issue Oct 3, 2023 · 1 comment
Labels
kind/epic Large new features or investments

Comments

@guineveresaenger
Copy link
Contributor

guineveresaenger commented Oct 3, 2023

During ops, we ran a bridge release and updated the bridge to all providers. Some updates were successful; others failed.

These are sorted by category and linked to the successful PR or failed Workflows.

Author Identity Unknown

This is a very frustrating occurrence where git cannot determine the identity of the runner in question.
Here's the issue for that: pulumi/upgrade-provider#144

No space left on device/ Runner received shutdown signal

Unsure if these are the same cause, but they're in a similar space.

make upstream failure

Filed in pulumi/upgrade-provider#172

Dirty Worktree

Not all of these have a similar diff!

Grab Bag

These all warrant more investigation on the provider

Merged After Rerun due to flaky python deps install

Issue for this in #650

Merged After A Third Rerun due to failure on setup script

Merged After Rerun due to a 502 on install-pulumi-cli

Issue for this in #652

Merged

I believe a human manually merged all these.

Summary

  • 25 merged, manually, with no issue

  • 9 merged after re-kicking flaky tests

  • 9 dirty work trees

  • 2 failure to find upstream go.mod

  • 3 runners struggling with the workload

  • 17 failed with git not accepting the identity of the runner attempting to open a PR

  • 3 triggered genuine breaking tests

@mikhailshilkov mikhailshilkov added the kind/epic Large new features or investments label Oct 4, 2023
@t0yv0
Copy link
Member

t0yv0 commented Oct 6, 2023

A lot of these fail because workflows are not merging. You wouldn't get newrelic to fail if pulumi/pulumi-newrelic#517 merged for example, but it's not auto merging. I think @mjeffryes was looking into making sure all workflows auto merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic Large new features or investments
Projects
None yet
Development

No branches or pull requests

3 participants