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

Mergify stall on getting-started local-npm failure #6014

Closed
mhofman opened this issue Aug 20, 2022 · 1 comment · Fixed by #8267
Closed

Mergify stall on getting-started local-npm failure #6014

mhofman opened this issue Aug 20, 2022 · 1 comment · Fixed by #8267
Assignees
Labels
bug Something isn't working tooling repo-wide infrastructure vaults_triage DO NOT USE

Comments

@mhofman
Copy link
Member

mhofman commented Aug 20, 2022

Describe the bug

We've now hit 2 cases of the getting-started local-npm test failing and Mergify not automatically backing out the PR and effectively stalling the queue.

To Reproduce

Steps to reproduce the behavior:

  1. See fix(SwingSet)!: Representatives inherit bound methods #5970 and 5992 internal package #6001 and associated conversations on slack

Expected behavior

Mergify automatically unqueueing a PR where these tests fail.

@mhofman mhofman added bug Something isn't working tooling repo-wide infrastructure labels Aug 20, 2022
@ivanlei ivanlei added the vaults_triage DO NOT USE label Dec 20, 2022
@mhofman mhofman linked a pull request Aug 29, 2023 that will close this issue
@mhofman mhofman closed this as completed Aug 29, 2023
@mhofman
Copy link
Member Author

mhofman commented Aug 29, 2023

Should be done with #8267

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tooling repo-wide infrastructure vaults_triage DO NOT USE
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants