Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Nov 10, 2022

🙁 This pull request has failed checks. #3927 will be removed from the queue. 🙁

Branch develop (990e519) and #3927 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #3927.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: message-relayer-tests
    • check-skipped=ci/circleci: message-relayer-tests
    • check-success=ci/circleci: message-relayer-tests
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: contracts-tests
    • check-skipped=ci/circleci: contracts-tests
    • check-success=ci/circleci: contracts-tests
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: core-utils-tests
    • check-skipped=ci/circleci: core-utils-tests
    • check-success=ci/circleci: core-utils-tests
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: dtl-tests
    • check-skipped=ci/circleci: dtl-tests
    • check-success=ci/circleci: dtl-tests
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: depcheck
    • check-skipped=ci/circleci: depcheck
    • check-success=ci/circleci: depcheck
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: indexer-tests
    • check-skipped=ci/circleci: indexer-tests
    • check-success=ci/circleci: indexer-tests
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: replica-healthcheck-tests
    • check-skipped=ci/circleci: replica-healthcheck-tests
    • check-success=ci/circleci: replica-healthcheck-tests
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: yarn-monorepo
    • check-skipped=ci/circleci: yarn-monorepo
    • check-success=ci/circleci: yarn-monorepo
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: contracts-bedrock-tests
    • check-skipped=ci/circleci: contracts-bedrock-tests
    • check-success=ci/circleci: contracts-bedrock-tests
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: contracts-governance-tests
    • check-skipped=ci/circleci: contracts-governance-tests
    • check-success=ci/circleci: contracts-governance-tests
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: contracts-periphery-tests
    • check-skipped=ci/circleci: contracts-periphery-tests
    • check-success=ci/circleci: contracts-periphery-tests
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: op-bindings-build
    • check-skipped=ci/circleci: op-bindings-build
    • check-success=ci/circleci: op-bindings-build
  • any of [🛡 GitHub branch protection]:
    • check-neutral=ci/circleci: devnet (with genesis contracts)
    • check-skipped=ci/circleci: devnet (with genesis contracts)
    • check-success=ci/circleci: devnet (with genesis contracts)
  • #approved-reviews-by>=2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success=pr-labeler
    • check-neutral=pr-labeler
    • check-skipped=pr-labeler
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: batch-submitter-tests
    • check-neutral=ci/circleci: batch-submitter-tests
    • check-skipped=ci/circleci: batch-submitter-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: bss-core-tests
    • check-neutral=ci/circleci: bss-core-tests
    • check-skipped=ci/circleci: bss-core-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: gas-oracle-tests
    • check-neutral=ci/circleci: gas-oracle-tests
    • check-skipped=ci/circleci: gas-oracle-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: geth-tests
    • check-neutral=ci/circleci: geth-tests
    • check-skipped=ci/circleci: geth-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: integration-tests
    • check-neutral=ci/circleci: integration-tests
    • check-skipped=ci/circleci: integration-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: proxyd-tests
    • check-neutral=ci/circleci: proxyd-tests
    • check-skipped=ci/circleci: proxyd-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=ci/circleci: teleportr-tests
    • check-neutral=ci/circleci: teleportr-tests
    • check-skipped=ci/circleci: teleportr-tests
  • any of [🛡 GitHub branch protection]:
    • check-success=security/snyk (Optimism)
    • check-neutral=security/snyk (Optimism)
    • check-skipped=security/snyk (Optimism)

More informations about Mergify merge queue can be found in the documentation.

Mergify commands

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the queue rules

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

---
pull_requests:
  - number: 3927
...

tynes and others added 3 commits November 9, 2022 14:35
This commit adds additional logging to the database
migration codepath. This is helpful for understanding
what is happening in the code, to understand how much
of the migration has already happened.

It may also help catch programmer/configuration errors,
although we should have testing to catch that and not
rely on the programmer watching the logs to catch issues.
@changeset-bot
Copy link

changeset-bot bot commented Nov 10, 2022

⚠️ No Changeset found

Latest commit: b1af822

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@mergify
Copy link
Contributor Author

mergify bot commented Nov 10, 2022

The pull request #3927 cannot be merged and has been disembarked.

@mergify mergify bot closed this Nov 10, 2022
@mergify mergify bot deleted the mergify/merge-queue/284e5dac74 branch November 10, 2022 04:58
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.

1 participant